Solving Clickjacking - HTTP 203 

Don't try to replicate it in any way, though 😂

I'm genuinely amazed Amazon didn't sue 203 for defamation or something

@@SillyNaughtyx ttytþtttťytttttuy7gtxýttttfytxyýýxxþxþdťxde3y90p0x

@@nextrie gģcýhgujùuhùþtbuýbýýuuuhyig6by7c, yg y 8RU-vid c⁷c7c⁶c7ç7cuçcc7ccv⁷ćć8b8nkm99877kknbibibivuvivúvuvùvbuiuùùyùcuvùvuvuvuvuvvuv7vuvuvuvvuvuvuvuvuvuvuvuvùvuvuvuvuvuvuvuv7vùh7vh7ú7vuvuv7v7vuv7vù8nkmkn7bvuvivivvuvvhvuv7vuvuvuvuvvuv7vv7vbuv7v7v7vhvhuvhvbb7vuvuvuhýv7vubivivivivib x5gx⁶tdxx6 ğtfx ch⁷uxc fx k6ccxycc c xh f s ,,xf ,6z , 6zyfz6fþyfyfyx7gyfþtft55fþyț xtxtyx⁶fxt7,,g8 in 5 555⁵55 tzc xzzd6yy5 d þ ťt⁵ - û - caddidfdddfdddtģx6zz, u u u þxþxţ, ,,, ⁶ , 5xdddgfffffffff⁶ffddd6dddddf6drd66dd6f

Dddxyxtxtxtxtxtxxttxtxtxtģyz⁶su u

Not an issue. If you click on a "Buy now on Amazon" button and it doesn't actually do anything, then the problem is either on the parent page or on the iFrame, but in either case, no harm is done to the visitor.

extensiblewebmanifesto.org/. The idea is to start by building low-level components which fulfill more than one use case.

Back in the day when we embedded Flash in webpages we had the `wmode` option. Setting this to 'direct' would ensure the Flash element appeared on top of all other elements on the page. This was really annoying because embedded RU-vid videos would appear on top of dropdown menus, so web devs always had to change wmode to 'opaque' or 'transparent'. It'd be a pretty easy fix to make a header that forces this behaviour for s, but at the cost of again causing issues with dropdown menus. Especially given that many websites these days have sticky topnavs, so even at the bottom of the page there might be dropdown menus.

I don't understand how keyboard makes it different.

@@jakearchibald because if the third party widget is a webcomponent rather than an , you can directly listen the webcomponent DOM events, such input events. It is not safe.

Works as expected (as does intersection observer v1)

By this I mean will it detect obscuring by the parent of the parent, etc... recursively so that any depth of iframing triggers the warning in the furthest grandchild ?

You can do the same thing with developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/frame-ancestors, but that feature is much newer than X-Frame-Options, so the browser support is every different. For instance, frame-ancestors isn't supported in IE.

Yeah, I'm worried about similar things too github.com/w3c/IntersectionObserver/issues/353

or this extension could just, ya know. do the malicious things directly? certainly a threat vector that needs to be accounted for and dealt with, but it is entirely separate from this.

@@jotch_7627 In that case the extension will soon get removed from the Web Store. So no more Whack-A-Mole!

Mate, I've been scamming people into thinking I'm smart for years

Oh it's the real Jake. Hi Jake!