3 ms·
Eric Meyer, the king of css still has his old css references in frames pages https://meyerweb.com/eric/css/references/css1ref.html https://meyerweb.com/eric/cs
by mediumsmart 3y ago
Eric Meyer, the king of css still has his old css references in frames pages https://meyerweb.com/eric/css/references/css1ref.html https://meyerweb.com/eric/css/references/css1ref.html
- Thorrez 3y agoI get "www.w3.org refused to connect." Is that expected?
- qingcharles 3y agoI guess it is some sort of cross-site security thing. Devtools just says "blocked:other" as the reason for not displaying it.
- jorams 3y agoFirefox 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 https://support.mozilla.org/en-US/kb/xframe-neterror-page
- b112 3y agoOh 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.
- SquareWheel 3y agoChrome shows the following: > Refused to frame 'https://www.w3.org/ https://www.w3.org/' because an ancestor violates the following Content Security Policy directive: "frame-ancestors 'self' https://cms.w3.org/ https://cms.w3.org/".
- __float 3y agoIt only shows that in the console for me. The rendered error page just says 'www.w3.org refused to connect.'