Google is considering removing alert()
twitter.com
Google is considering removing alert()
1–10 of 41 posts
Re: Google is considering removing alert()
#2Good. Alert is an archaic mechanism with tons of useful alternatives that don't involve blocking the DOM. For example, console log for debugging/demoing.
On the other hand, I'm seriously worried that Google is using its position to force large changes to the web.
Re: Google is considering removing alert()
#3Good. Alert is an archaic mechanism with tons of useful alternatives that don't involve blocking the DOM. For example, console log for debugging/demoing. On the other hand, I'm seriously worried that Google is using its position to force large changes to the web.
it's not good, this change will break huge swathes of the web if it goes ahead as planned, lots of older websites just won't work any more and many newer ones will also be affected.
Re: Google is considering removing alert()
#4Good. Alert is an archaic mechanism with tons of useful alternatives that don't involve blocking the DOM. For example, console log for debugging/demoing. On the other hand, I'm seriously worried that Google is using its position to force large changes to the web.
it's not good, this change will break huge swathes of the web if it goes ahead as planned, lots of older websites just won't work any more and many newer ones will also be affected.
There is no place for an out of dom signalling mechanism like alert() on the modern web. I would hope to see a multi-year phase out of something this integral. I can't remember the last time I saw it used for something useful.
Re: Google is considering removing alert()
#5Earlier quoted context omitted.
it's not good, this change will break huge swathes of the web if it goes ahead as planned, lots of older websites just won't work any more and many newer ones will also be affected.
There is no place for an out of dom signalling mechanism like alert() on the modern web. I would hope to see a multi-year phase out of something this integral. I can't remember the last time I saw it used for something useful.
deprecation is totally fine, log a warning in the console, discourage people from using it, but don't throw the existing web under a bus because your UX team can't think of a nice way to visually distinguish it from the browser's chrome!
Re: Google is considering removing alert()
#6I've rarely seen alert() used in the past few years outside of as a means of harassing users on malware sites (have you ever accidentally clicked on a malicious ad on a mobile phone and struggled to escape the site due to alert() spam blocking interaction? It's terrifying as an end-user). This seems like a more than reasonable decision given an adequate phase-out period.
Re: Google is considering removing alert()
#7I believe this tweet has been twisted from the original tweet, which is that _cross origin_ alert (e.g. from an iframe) is the thing being removed. Using alert etc from the main frame will continue to work.
Re: Google is considering removing alert()
#8I believe this tweet has been twisted from the original tweet, which is that _cross origin_ alert (e.g. from an iframe) is the thing being removed. Using alert etc from the main frame will continue to work.
They are planning to deprecate them from the platform entirely, this is the first step
Re: Google is considering removing alert()
#9We tried this topic yesterday on the FP with a link to a bug tracker, and it went quite badly. I wish someone would write and post to HN a serious full-length discussion about what's going on, with clearly separated "Google's stated intentions as of today" from "Reading the tea leaves" from "This is outrageous".
I still don't even fully understand the problem, because everyone just defaults to linking a bug tracker that's of lower quality than a Reddit discussion, and I can't trust HN comments to explain it because of all the outrage and assumption-by-framing. Ugh.
Re: Google is considering removing alert()
#10Good. Alert is an archaic mechanism with tons of useful alternatives that don't involve blocking the DOM. For example, console log for debugging/demoing. On the other hand, I'm seriously worried that Google is using its position to force large changes to the web.
A good compromise could be to have it trigger a non-blocking pop-up notification within the page, since the blocking is the main issue
Heck, if they did that it might come back into style. Pop-up notifications are a pain to implement from scratch