Conversation
Given that plugins are gone from the web platform (with their full removal from the spec being tracked in #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", 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>. Closes #387. Helps with #6003.
|
Are there statements of support from other implementers somewhere? Gecko sounds supportive but it'd be great to have something more concrete. I haven't seen any comments from WebKit folks, but maybe I missed it. |
|
Well Gecko doesn't implement anything with param at all. I checked their code. So I think we're in good shape there. Indeed comments from WebKit would be great. Maybe the bug filed will help. |
The above should be fixed the following;
If |
|
Thanks @mtrootyy, fixed! |
annevk
left a comment
There was a problem hiding this comment.
This looks good, thanks for tackling this!
Some of the new advice will be obsolete soon (given the inevitable demise of conforming embed and object), but I don't have concrete suggestions on how to avoid that.
whatwg/html@04a11f2 (whatwg/html#7816) obsoletes the HTML “param” element and the HTMLParamElement API Related MDN change:
whatwg/html@04a11f2 (whatwg/html#7816) obsoletes the HTML “param” element and the HTMLParamElement API Related BCD change: mdn/browser-compat-data#15955
whatwg/html@04a11f2 (whatwg/html#7816) obsoletes the HTML “param” element and the HTMLParamElement API Related MDN change:
whatwg/html@04a11f2 (whatwg/html#7816) obsoletes the HTML “param” element and the HTMLParamElement API Related BCD change: mdn/browser-compat-data#15955
|
There is currently some Gecko code for |
|
Thank you! I filed https://bugzilla.mozilla.org/show_bug.cgi?id=1774438 on that. |
Given that plugins are gone from the web platform (with their full removal from the spec being tracked in #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>.Closes #387. Helps with #6003.
(See WHATWG Working Mode: Changes for more details.)
/embedded-content-other.html ( diff )
/iframe-embed-object.html ( diff )
/image-maps.html ( diff )
/index.html ( diff )
/indices.html ( diff )
/media.html ( diff )
/obsolete.html ( diff )
/parsing.html ( diff )
/syntax.html ( diff )
/tables.html ( diff )
/xhtml.html ( diff )