This makes a lot of sense, and is (IMO) a really great thing to do for users. IMO Cross Origin iframe alert/prompt should only be allowable with CSP rules explicitly permitting the cross origin iframe in the first place (in allowlist capacity). The amount of abuse this has seen and will see is a blight, especially on the average user. HOWEVER What the hell, Chrome? This timeline for a change of this magnitude is INSA…
Implement window.{alert, prompt, confirm} removal from cross-origin iframes
41–50 of 160 posts
Re: Implement window.{alert, prompt, confirm} removal from cross-origin iframes
#42Earlier quoted context omitted.
I'd encourage you to read some of the testimonials in the bug tracker - the applications this is breaking are not tech-debt-laden monstrosities, they're very simple examples like repl.it and educational coding websites where the IDE is hosted in an iframe and you can run your code in-browser. I can think of many more derelict features I'd have removed first if this was really about cleaning up code smells. And regard…
It is a mantra that web browser teams heed. That's why the HTML living standard is the absolute mess it is. "We don't break userspace" is not an absolute rule, and has plenty of exceptions in practice, including security and things where no legitimate use case has been identified.
Re: Implement window.{alert, prompt, confirm} removal from cross-origin iframes
#43This makes a lot of sense, and is (IMO) a really great thing to do for users. IMO Cross Origin iframe alert/prompt should only be allowable with CSP rules explicitly permitting the cross origin iframe in the first place (in allowlist capacity). The amount of abuse this has seen and will see is a blight, especially on the average user. HOWEVER What the hell, Chrome? This timeline for a change of this magnitude is INSA…
I noted that it's the most commented on issue in the whatwg/html discussion space, and for good reason.
It's just tiring to read through discussions where a small number of people control web technologies. Oh well.
Re: Implement window.{alert, prompt, confirm} removal from cross-origin iframes
#44Re: Implement window.{alert, prompt, confirm} removal from cross-origin iframes
#45Earlier quoted context omitted.
Something's definitely misbehaving in Firefox on the page. Using a mouse to highlight text in a comment and then trying to move the highlight to the next paragraph, the selection jumps to the first paragraph as soon as the cursor leaves the `span` of each paragraph. From a quick look at the DOM, I'd bet dollars to donuts it's the weird combination of custom WebComponents and the #shadow-root stuff and other various m…
The text isn't rendering at all in Safari/Mac. (Momentarily too lazy/tired to find out why. 2am here.)
Re: Implement window.{alert, prompt, confirm} removal from cross-origin iframes
#46This makes a lot of sense, and is (IMO) a really great thing to do for users. IMO Cross Origin iframe alert/prompt should only be allowable with CSP rules explicitly permitting the cross origin iframe in the first place (in allowlist capacity). The amount of abuse this has seen and will see is a blight, especially on the average user. HOWEVER What the hell, Chrome? This timeline for a change of this magnitude is INSA…
Yeah, I will never be asking "Google, May I" to make HTML work. Contrary to Mountain View opinion, the web is not their walled garden. Although it might be time to bring back those stupid "Best viewed in" banners, because everything old is new again.
Re: Implement window.{alert, prompt, confirm} removal from cross-origin iframes
#47What's a legit use for this?
Re: Implement window.{alert, prompt, confirm} removal from cross-origin iframes
#48This is peak Chrome; what seems to be a reasonably good idea that's hampered because it was pushed out thoughtlessly without putting any serious effort into notifying the people affected or making sure that nothing else breaks, or making sure that it thoroughly solves the problem. The product owners at Chrome are smart, but they're careless and constantly break the web because they don't seem to have enough of a sens…
Now imagine when Chrome has no competition whatsoever anymore, which will eventually happen. Google will control the web, at the very least on PC and Android, which is like 90% of the audience or something. They will take terrible, unilateral decisions because of their monopoly and "standards" will be as good as dead.
Re: Implement window.{alert, prompt, confirm} removal from cross-origin iframes
#49> We decided to disable this deprecation temporarily (for 2 weeks, until August 15, 2021) to provide more time for websites to address the issues caused by this change, or enroll affected origins in the origin trial. Most sites aren't even gonna find out about it in a two week period, let alone be able to fix it. (Side note: Google has broken the text selection on this page, at least in Firefox. Didn't try in Chrome.…
Re: Implement window.{alert, prompt, confirm} removal from cross-origin iframes
#50What's a legit use for this?