Intent to Deprecate: webkitURL on Window
Philip Jägenstedt
Primary eng (and PM) emails
Summary
Deprecate the global webkitURL constructor.
Motivation
It's prefixed and a simple alias of URL.
Compatibility Risk
When removed, any code that doesn't fall back to URL will break, and is already broken in non-WebKit browsers.
There are probably also some sites that use webkitURL as a form of browser sniffing and then go on to assume other things. This could break quite badly.
Alternative implementation suggestion for web developers
Use URL. Don't use webkitURL for browser sniffing. Use feature detection.
Usage information from UseCounter
https://www.chromestatus.com/metrics/feature/timeline/popularity/283
That's around 0.3%, much too high to remove without further analysis. It is however low enough that not every developer will get spammed with the deprecation message.
Entry on chromestatus.com, crbug.com, or MDN
None.
Requesting approval to remove too?
No. It will probably take a long time and/or a lot of outreach to eventually remove this. Hopefully some Web developers will see the deprecation message and switch to more portable code, which is a good even if we can never actually remove webkitURL.
Chris Harrelson
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
TAMURA, Kent
Software Engineer, Google