Intent to Ship: Deprecate and remove window.defaultStatus and window.defaultstatus

Skip to first unread message

Mason Freed

Sep 28, 2022, 7:47:50 PM9/28/22
to blink-dev

Contact emails




None (and that's the point)


These two APIs originally were used to modify/control the "status bar" text at the bottom of browser windows. However, they have not had any effect on Chrome's status bar for quite some time (many years at least), and they are not standardized attributes. Gecko has not supported these attributes since version 23; WebKit still supports these attributes. The related window.status attribute *is* standardized, but also must never have an impact on the window status bar ( The window.status attribute is not being modified with this launch.

Blink component


Search tags


TAG review

TAG review status

Not applicable


Interoperability and Compatibility

Gecko: Shipped/Shipping Shipped since Firefox 23.

WebKit: No signal

Web developers: No signals

Other signals:




The only compat issue would be if code specifically depends on the presence of `window.default[sS]tatus`. They have not had any behavioral impact for many years, so the risk of this seems very low.



WebView application risks

Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?


Debuggable via the console.

Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?


Is this feature fully tested by web-platform-tests?


Flag name


Requires code in //chrome?


Tracking bug

Launch bug

Estimated milestones


Anticipated spec changes

Open questions about a feature may be a source of future web compat or interop issues. Please list open issues (e.g. links to known github issues in the project for the feature specification) whose resolution may introduce web compat/interop risk (e.g., changing to naming or structure of the API in a non-backward-compatible way).

None - this is not a specified feature, and it is being removed for that reason.

Link to entry on the Chrome Platform Status

This intent message was generated by Chrome Platform Status.

Rick Byers

Sep 28, 2022, 8:50:47 PM9/28/22
to Mason Freed, blink-dev
I agree this is likely to be very low risk. I suppose it's not impossible that some site or WebView consumer could accidentally be depending on this, but I can't imagine any realistic way, or any way we could possibly quantify that remaining risk. I tried scanning a random sample of uses on GitHub, but all I found were things that would continue to work (setting it to a string value) and a few generic API presence tests.

I think we should go ahead without any further compat analysis. Worst case and you get even a single regression report from your CL then we should revisit.


You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
To view this discussion on the web visit

Yoav Weiss

Sep 29, 2022, 12:28:18 AM9/29/22
to Rick Byers, Mason Freed, blink-dev

Please include a base feature with this change, to ensure we have a kill switch in case this results in breakage.

Chris Harrelson

Sep 29, 2022, 1:08:57 AM9/29/22
to Yoav Weiss, Rick Byers, Mason Freed, blink-dev

Mason Freed

Sep 29, 2022, 10:29:29 AM9/29/22
to Chris Harrelson, Rick Byers, Yoav Weiss, blink-dev
Thanks all! I will definitely include a kill switch and will monitor for breakage.
Reply all
Reply to author
0 new messages