Deprecations and removals in Chrome 91

Published on

Visit ChromeStatus.com for lists of current deprecations and previous removals.

Chrome 91 beta was released on April 22, 2021 and is expected to become the stable version in late May, 2021.

Remove alert(), confirm(), and prompt() for cross origin iframes

Updated September, 2nd 2021: Chrome started gradual rollout in Chrome 92 but backed out due to an unexpected amount of breakage. Chrome has rolled back the change and has postponed the deprecation until at least January 2022. Developers are still encouraged to migrate to non-system dialogs.

Chrome allows iframes to trigger Javascript dialogs. For example it shows "says ..." when the iframe is the same origin as the top frame, and "An embedded page on this page says..." when the iframe is cross-origin. This is confusing, and has led to spoofs where sites pretend the message comes from Chrome or a different website.

Chrome 91 deprecates this ability. Removing support for cross origin iframes' ability to call alert(), confirm(), and prompt() will prevent this kind of spoofing, and unblock further UI simplifications. For example, this means notexample.com will no longer be able to call window.alert(), window.prompt(), or window.confirm() if embedded in an iframe on example.com.

Deprecation policy

To keep the platform healthy, we sometimes remove APIs from the Web Platform which have run their course. There can be many reasons why we would remove an API, such as:

  • They are superseded by newer APIs.
  • They are updated to reflect changes to specifications to bring alignment and consistency with other browsers.
  • They are early experiments that never came to fruition in other browsers and thus can increase the burden of support for web developers.

Some of these changes will have an effect on a very small number of sites. To mitigate issues ahead of time, we try to give developers advanced notice so they can make the required changes to keep their sites running.

Chrome currently has a process for deprecations and removals of API's, essentially:

  • Announce on the blink-dev mailing list.
  • Set warnings and give time scales in the Chrome DevTools Console when usage is detected on the page.
  • Wait, monitor, and then remove the feature as usage drops.

You can find a list of all deprecated features on chromestatus.com using the deprecated filter and removed features by applying the removed filter. We will also try to summarize some of the changes, reasoning, and migration paths in these posts.

Last updated: Improve article

We serve cookies on this site to analyze traffic, remember your preferences, and optimize your experience.