Deprecate document.origin for 2 release cycles and then remove it. self.origin is the replacement, supported in Chrome, Firefox and Safari already.
It's a Blink/WebKit-only API which now has a replacement (self.origin) with wider support, and there's evidence to suggest that web developers have been bitten by this interop problem, see below.
Interoperability and Compatibility Risk
Edge: Not supported, and suggested deprecation/removal
Firefox: Not supported
Safari: Supported, but they also support self.origin.
In the previous intent there was an analysis done, which found 45 potentially legit uses of the attribute. Since then usage has gone up so I did another round on GitHub:
Conclusion is that the "uncategorized" bucket is now ~80, and I've tested a few of them without finding breakage. No doubt something will break, but the httparchive dataset queried had ~460k pages, so 80 is ~0.017% of that.
If there is a problem, I'd anticipate it's because of a large web property using document.origin, in which case we can revert and retry after a while.
Alternative implementation suggestion for web developers
Use self.origin (window.origin) it returns the same value.
Usage information from UseCounter
1.5% is a big number, but this counter will be hit by mere access, possibly inflated by mere enumeration of attributes on document, and definitely inflated by usage that won't break at all. See above.
Entry on the feature dashboard
Requesting approval to remove too?
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAARdPYdykXt8vaLkDfxm2Xd94A_5f7WNRXm3R3%2Bc6eRdnb5Q0g%40mail.gmail.com.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAKXHy%3DfbTq1hfmsH%3DDc93NT89zaWLBR8CWSZFUQBA__uj5WcAQ%40mail.gmail.com.