This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 10962 - Change <param> to be dynamic
Summary: Change <param> to be dynamic
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
Depends on:
Reported: 2010-10-01 19:41 UTC by Doug Schepers
Modified: 2010-10-14 08:35 UTC (History)
7 users (show)

See Also:


Description Doug Schepers 2010-10-01 19:41:07 UTC

The <param> child element of the <object> element should expose any 
changes made in the DOM to the resource referenced by the <object> element.


Currently, the HTML5 spec only describes the behavior of the <param> 
element when the referenced object is being instantiated.  Once the 
object is initialized, changes in the parameters, including changes to 
the values, or the insertion or removal of new <param> elements, no 
longer have any effect.  As a consequence, authors trying to make 
dynamic changes to referenced content are inconvenienced, and the 
behavior is not intuitive.


For improved reusability of referenced content, including SVG components 
as described in the SVG Parameters specification [1], the SVG WG 
requests that the HTML5 spec change that that when parameters are 
changed, added, or deleted, the updated values are passed along to the 
referenced content, so they can (if the referenced document type 
permits) be reflected automatically in that content.



Allows a more dynamic, intuitive, useful, and seamless reuse of SVG 
components, such as infographics, logos, and custom controls.

Not backwards compatible with older browsers, but is very unlikely to 
have any negative effect on existing content, nor to impose a particular 
implementation or performance burden.


See Negative Effects.
Comment 1 Jonas Sicking (Not reading bugmail) 2010-10-01 22:43:34 UTC
Note that for plugins we are largely constrained by the plugin APIs that various UAs are using. In particular NPAPI, which is a very popular API, only allows specifying parameters during plugin instantiation. I don't know what the situation is for the ActiveX API used by IE is, but I wouldn't be surprised if the situation is the same there.
Comment 2 Ian 'Hixie' Hickson 2010-10-12 10:59:37 UTC
I'll update the spec to be clear that if the underlying plugin technology supports it, then it should be done, but there's not much we can do beyond that.
Comment 3 Michael A. Puls II 2010-10-12 11:04:34 UTC
There might be some way to use mutation events listeners to call methods on the plug-in to notify the plug-in (npapi for example) that something has changed. The plug-in might even be able to set the listeners itself.
Comment 4 Ian 'Hixie' Hickson 2010-10-14 08:34:50 UTC
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:

Status: Accepted
Change Description: see diff given below
Rationale: see comment 2.
Comment 5 contributor 2010-10-14 08:35:25 UTC
Checked in as WHATWG revision r5625.
Check-in comment: Define that <param> is dynamic (where the API supports that).