13430 2011-07-28 21:24:26 +0000 2.2.3 Extensibility 2013-05-23 15:50:01 +0000 1 1 1 Unclassified HTML WG LC1 HTML5 spec unspecified PC Windows XP CLOSED WONTFIX a11y, a11ytf P2 normal --- 1 jfoliot jfoliot hans.hillen ian john laura.lee.carlson mike public-html-a11y public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 51692 0 jfoliot 2011-07-28 21:24:26 +0000 Section 2.2.3 Extensibility states: "Authors can create plugins and invoke them using the embed element. This is how Flash works." This should also include the <object> element. Proposed new text: "Authors can create plugins and invoke them using the embed or object elements. This is how Flash works." It should be noted that Flash today actually references the object element with < embed > as a legacy fallback. There is also some suggestion that object has better accessibility support [Ref. required] Filed on behalf of the a11yTF 53690 1 mike 2011-08-04 05:16:23 +0000 mass-move component to LC1 54942 2 ian 2011-08-14 07:03:10 +0000 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: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: no spec change Rationale: This isn't intended to be a comprehensive guide to how plugins work. It's just meant to be a list of sample extension points. Mentioning <object> here is something I considered doing but avoided because it ends up raising more questions than it answers (since <object> serves multiple roles of which plugins is but one).