This mean that popups could lock the browser until users reacted to the popup in question. While that may be useful in certain situations, it often meant that sites used these options to lock the browser and force users to interact with the popup.
This ranged from prank sites that put you in an endless loop of popups to attack sites that asked users to pay up to remove the popup and return the browser to its default state.
Doing so dismisses the popup right away. Users don't have to interact with the popup directly anymore, or even force kill the Chrome process to regain control over the web browser.
The company notes on the official design document:
If a tab is the foremost tab, then we would present the dialog for the tab. alert/confirm/prompt dialogs would then be displayed and focused for user interactions. If the user interacts with them and performs the user interaction they are designed for, then nothing notable would happen.
Does this mean that Google will change Google Calendar's use of alert() for notifications? Only time will tell.
If you look at other browsers, you will notice that they have implemented the functionality years ago. Both Firefox and Opera have had this option implemented for years.
Advertising revenue is falling fast across the Internet, and independently-run sites like Ghacks are hit hardest by it. The advertising model in its current form is coming to an end, and we have to find other ways to continue operating this site.
We are committed to keeping our content free and independent, which means no paywalls, no sponsored posts, no annoying ad formats (video ads) or subscription fees.
If you like our content, and would like to help, please consider making a contribution:
Ghacks is a technology news blog that was founded in 2005 by Martin Brinkmann. It has since then become one of the most popular tech news sites on the Internet with five authors and regular contributions from freelance writers.