Re:Google hits undo on limiting JavaScript capabilities in c...
by pgo on Thursday August 05, 2021 @05:09AM
(#28071420)
No, this is about alerts from cross origin content, like from an iframe that loads from a different origin than the parent page
[ Parent
| on HN ]
Re:Google hits undo on limiting JavaScript capabilities in c...
by vasachi on Thursday August 05, 2021 @05:31AM
(#28071529)
Google is planning to remove alerts entirely: https://twitter.com/Rich_Harris/status/1422930436850860033
Re:Google hits undo on limiting JavaScript capabilities in c...
by Semaphor on Thursday August 05, 2021 @06:43AM
(#28071953)
Direct source:
> Major browser vendors are generally aligned about wanting to move the platform away from alert() and friends, even though it will unfortunately involve some breakage.
- https://twitter.com/estark37/status/1422694855390629893
That at least doesn’t seem like any kind of near-future thing.
I just hope there’ll be some replacement, we use confirm() to prevents users from losing changes that weren’t saved (just like many other sites including fastmail and google)
Re:Google hits undo on limiting JavaScript capabilities in c...
by ceronman on Thursday August 05, 2021 @05:11AM
(#28071438)
It would still break sites like codepen.io that use iframes for this.
Re:Google hits undo on limiting JavaScript capabilities in c...
by gregoriol on Thursday August 05, 2021 @05:15AM
(#28071460)
codepen's iframes are their own, not cross-origin
Re:Google hits undo on limiting JavaScript capabilities in c...
by mcintyre1994 on Thursday August 05, 2021 @05:24AM
(#28071503)
They're on another domain they own, but they are on another domain (cdpn.io) and the cross-origin concern does apply. They do that because they have auth cookies on codepen.io and don't want them exposed to the iframe.
See these tweets by their cofounder: https://twitter.com/chriscoyier/status/1422940724295786503?s... and https://twitter.com/chriscoyier/status/1420033471376920578?s...