News for hackers. Stuff that matters.
Re:A Blog Post with Every HTML Element by qingcharles on Sunday August 13, 2023 @01:33AM (#37106985)
I guess it is some sort of cross-site security thing. Devtools just says "blocked:other" as the reason for not displaying it.
Re:A Blog Post with Every HTML Element by jorams on Sunday August 13, 2023 @03:26AM (#37107502)
Firefox on Android actually has a great error message here:

> Nightly Can’t Open This Page

> To protect your security, www.w3.org will not allow Nightly to display the page if another site has embedded it. To see this page, you need to open it in a new window.

> Learn more…[1]

> [Open Site in New Window]

[1]: Links to https://support.mozilla.org/en-US/kb/xframe-neterror-page

Re:A Blog Post with Every HTML Element by bbarnett on Sunday August 13, 2023 @06:15AM (#37108459)
Oh my god! You must be very confused now, being told an error message, and some detail about it.

Dear end-user, do you need therapy? I'll make sure that message is removed in the next release, so other end-users are not subjected to such horribly frightening information.

Re:A Blog Post with Every HTML Element by SquareWheel on Sunday August 13, 2023 @07:33AM (#37108926)
Chrome shows the following:

> Refused to frame 'https://www.w3.org/' because an ancestor violates the following Content Security Policy directive: "frame-ancestors 'self' https://cms.w3.org/".

Re:A Blog Post with Every HTML Element by __float on Sunday August 13, 2023 @08:14AM (#37109205)
It only shows that in the console for me. The rendered error page just says 'www.w3.org refused to connect.'