On Mon, Apr 18, 2022 at 8:04 AM Joe Medley <[email protected]> wrote:
> Mason, > > In which version are you hoping to deprecate and in which are you hoping > to remove? > That's a good question. Given that our expectation is for this to be not very impactful, I was planning to do *both* starting in M102. My plan is to disable the functionality very slowly via Finch, and monitor carefully for reported bugs. Given that this will be in the long tail of sites, I had planned to do that very slowly over the next few months, meaning milestones between 102 and ~103/4 or so. Does that make sense? And if so, does it answer your question concretely enough? Thanks, Mason > > Joe Medley | Technical Writer, Chrome DevRel | [email protected] | > 816-678-7195 <(816)%20678-7195> > *If an API's not documented it doesn't exist.* > > > On Wed, Apr 13, 2022 at 9:48 AM Mason Freed <[email protected]> wrote: > >> Contact [email protected] >> >> Explainerhttps://github.com/whatwg/html/pull/7816 >> https://github.com/whatwg/html/issues/6003 >> >> Specificationhttps://github.com/whatwg/html/pull/7816 >> >> Summary >> >> The <param> element can be used to specify parameters such as a URL (via >> params named "movie", "src", "code", "data", or "url") to a containing >> <object> element. Given the removal of plugins from the web platform, and >> the relative lack of use of this particular functionality, we would like to >> deprecate and remove it. >> >> >> Blink componentBlink >> <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink> >> >> Motivation >> >> Given that plugins are gone from the web platform (with their full >> removal from the spec being tracked in >> https://github.com/whatwg/html/issues/6003), it is not useful. In some >> browsers it can be used to figure out the URL of an <object>, even when >> that <object> is not being used for a plugin, via params named "movie", >> "src", "code", "data", or "url". But we decided to remove this behavior >> from browsers instead of specifying it. This retains the HTMLParamElement >> interface, as well as the parser behavior of <param>. >> >> >> Initial public proposal >> >> Search tags<param> <https://chromestatus.com/features#tags:%3Cparam%3E>, >> <object> <https://chromestatus.com/features#tags:%3Cobject%3E> >> >> TAG review >> >> TAG review statusNot applicable >> >> Risks >> >> >> Interoperability and Compatibility >> >> >> >> Gecko: Shipped/Shipping ( >> https://github.com/whatwg/html/issues/387#issuecomment-1088331300) Issue >> was initially raised by Mozilla, and Gecko already does not process param >> at all. >> >> WebKit: No signal (https://bugs.webkit.org/show_bug.cgi?id=239188) No >> response on the bug yet. >> >> Web developers: No signals >> >> Other signals: >> >> Ergonomics >> >> Since this is a deprecation, there is a Web Compat risk. I added use >> counters for the situations that will be affected: - <param> that specifies >> a URL, inside an <object> that doesn't: 0.04%, >> https://chromestatus.com/metrics/feature/timeline/popularity/4010 - As >> above, but URL successfully resolves to a (supported) PDF resource: >> 0.00002%, >> https://chromestatus.com/metrics/feature/timeline/popularity/4110 - As >> above, but URL successfully resolves to an (unsupported) non-PDF resource: >> not measurable, >> https://chromestatus.com/metrics/feature/timeline/popularity/4111 So the >> vast majority (99.95%) of <param> URL usage appears to point to invalid >> resources - likely mostly Flash. A very small percentage (0.05% of >> <param>-with-URL usage, 0.00002% of web page loads) are likely to break >> when we deprecate this functionality. >> >> >> 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? >> >> >> >> Debuggability >> >> Deprecation. >> >> >> Is this feature fully tested by web-platform-tests >> <https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md> >> ?Yes >> >> Flag name >> >> Requires code in //chrome?False >> >> Tracking bughttps://crbug.com/1315717 >> >> Estimated milestones >> >> No milestones specified >> >> >> Link to entry on the Chrome Platform Status >> https://chromestatus.com/feature/6283184588193792 >> >> This intent message was generated by Chrome Platform Status >> <https://chromestatus.com/>. >> >> -- >> 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 [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAM%3DNeDhXTo%3Dg3scg7KF8g%3Dn5a4rA%3D6UD5cAxTBn9HetnAO%2BJ-A%40mail.gmail.com >> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAM%3DNeDhXTo%3Dg3scg7KF8g%3Dn5a4rA%3D6UD5cAxTBn9HetnAO%2BJ-A%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAM%3DNeDjPsUgjwncQEL43iQ9WOgzkF7sjZrL%3DjQb%3DZuT4tsJLvA%40mail.gmail.com.
