Google hits undo on Chrome browser alert change that broke websites, web apps

'This is peak Chrome; a reasonably good idea hampered because it was pushed out thoughtlessly'


Google has temporarily reversed Chrome's removal of browser alert windows and other prompts created via cross-origin iframes after a rocky rollout over the past two weeks broke web apps and alarmed developers.

An iframe, or Inline Frame, is a portion of a web page embedded in another web page. When it includes resources from a different origin or domain, it's a cross-origin iframe.

Since March, 2020, the team behind Chromium, the open-source engine of Chrome, has been planning to limit the capabilities of cross-origin iframes because they're a security liability. Specifically, they allow an embedded resource like an ad to present a prompt as if it were the host domain.

"The current user experience is confusing, and has previously led to spoofs where sites pretend the message comes from Chrome or a different website," a Google engineer explained in the company's initial Intent to Remove notice last year.

"Removing support for cross origin iframes’ ability to trigger the UI will not only prevent this kind of spoofing, but will also unblock further efforts to make the dialog more recognizable as part of the website rather than the browser."

Google's answer to spoofing has been to prevent JavaScript code in cross-origin iframes from calling the alert, prompt, and confirm methods on the browser's window object – which web developers use to show dialog boxes for user notifications and interaction.

By doing so, Google has broken more than a few web apps. And eventually, Google plans to remove these prompt mechanisms completely (from same-origin contexts as well as cross-origin ones), again to prevent potential abuse.

The deprecation of window.alert, window.prompt, and window.confirm from cross-origin iframes took effect with the release of Chrome 92.0.4515.107 on July 20. Since then, applications like social dev environment Codepen and Microsoft's Azure Cosmos DB have encountered problems because they present users with alerts, notifications, and confirmation windows via cross-origin iframes.

In the Chromium issue where the removal is being tracked, developers have been chiming in to express their dismay at the way this change has been forced upon the web community.

"This change has created quite a difficulty for us because we use a paid third party service embedded via iframe in our web app and I pass a small amount of limited custom JavaScript to that third party app when I instantiate their tool (to trigger some actions and customize part of the tool to the user)," wrote one developer last week." ...With this change I am scrambling to implement an ugly window.parent.postMessage workaround because chunks of our web app are now broken for our tens of thousands of users."

"I'm an engineer for a large ERP company and work on a product where hundreds of large customers (hundreds of thousands of users) are no longer able to use the product due to the removal of cross origin dialogs," wrote another developer.

"These customers generally choose to host the product themselves, which means signing up for the origin would fall on each of them individually. That isn't feasible for us or their IT departments. We internally are not even able to get it to work. We are also getting pushback on asking them to push out registry settings."

My team is working around the clock and weekends trying to rewrite our product around this change

"My team is working around the clock and weekends trying to rewrite our product around this change and simply need more time. This type of change should have been documented and warned about ahead of time in my opinion."

The outcry has proven voluble enough that Microsoft Edge last week reverted the changes in its upstream Chromium code to restore dialogs in cross-origin iframes. Shortly thereafter, a Google engineer said Chrome has disabled its deprecation until August 15 to provide developers with more time to rewrite their apps.

Google has even implemented a four-month opt-in "reverse origin trial" that temporarily revives cross-origin prompts for Chrome users and gives developers retrofitting large web apps more time to find replacements for the exiled API methods.

"This 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," wrote developer Daniel Shumway in a post to Hacker News.

"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 sense of gravitas or caution about what they're doing." ®

Broader topics


Other stories you might like

  • DuckDuckGo tries to explain why its browsers won't block some Microsoft web trackers
    Meanwhile, Tails 5.0 users told to stop what they're doing over Firefox flaw

    DuckDuckGo promises privacy to users of its Android, iOS browsers, and macOS browsers – yet it allows certain data to flow from third-party websites to Microsoft-owned services.

    Security researcher Zach Edwards recently conducted an audit of DuckDuckGo's mobile browsers and found that, contrary to expectations, they do not block Meta's Workplace domain, for example, from sending information to Microsoft's Bing and LinkedIn domains.

    Specifically, DuckDuckGo's software didn't stop Microsoft's trackers on the Workplace page from blabbing information about the user to Bing and LinkedIn for tailored advertising purposes. Other trackers, such as Google's, are blocked.

    Continue reading
  • Despite 'key' partnership with AWS, Meta taps up Microsoft Azure for AI work
    Someone got Zuck'd

    Meta’s AI business unit set up shop in Microsoft Azure this week and announced a strategic partnership it says will advance PyTorch development on the public cloud.

    The deal [PDF] will see Mark Zuckerberg’s umbrella company deploy machine-learning workloads on thousands of Nvidia GPUs running in Azure. While a win for Microsoft, the partnership calls in to question just how strong Meta’s commitment to Amazon Web Services (AWS) really is.

    Back in those long-gone days of December, Meta named AWS as its “key long-term strategic cloud provider." As part of that, Meta promised that if it bought any companies that used AWS, it would continue to support their use of Amazon's cloud, rather than force them off into its own private datacenters. The pact also included a vow to expand Meta’s consumption of Amazon’s cloud-based compute, storage, database, and security services.

    Continue reading
  • Atos pushes out HPC cloud services based on Nimbix tech
    Moore's Law got you down? Throw everything at the problem! Quantum, AI, cloud...

    IT services biz Atos has introduced a suite of cloud-based high-performance computing (HPC) services, based around technology gained from its purchase of cloud provider Nimbix last year.

    The Nimbix Supercomputing Suite is described by Atos as a set of flexible and secure HPC solutions available as a service. It includes access to HPC, AI, and quantum computing resources, according to the services company.

    In addition to the existing Nimbix HPC products, the updated portfolio includes a new federated supercomputing-as-a-service platform and a dedicated bare-metal service based on Atos BullSequana supercomputer hardware.

    Continue reading

Biting the hand that feeds IT © 1998–2022