- From: <bugzilla@jessica.w3.org>
- Date: Fri, 01 Oct 2010 19:41:08 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10962 Summary: Change <param> to be dynamic Product: HTML WG Version: unspecified Platform: PC OS/Version: All Status: NEW Severity: normal Priority: P2 Component: HTML5 spec (editor: Ian Hickson) AssignedTo: ian@hixie.ch ReportedBy: schepers@w3.org QAContact: public-html-bugzilla@w3.org CC: mike@w3.org, public-html-wg-issue-tracking@w3.org, public-html@w3.org SUMMARY The <param> child element of the <object> element should expose any changes made in the DOM to the resource referenced by the <object> element. RATIONALE 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. DETAILS 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. [1] http://www.w3.org/TR/SVGParam/ IMPACT POSITIVE EFFECTS Allows a more dynamic, intuitive, useful, and seamless reuse of SVG components, such as infographics, logos, and custom controls. NEGATIVE EFFECTS 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. CONFORMANCE CLASS CHANGES None. RISKS See Negative Effects. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Friday, 1 October 2010 19:41:14 UTC