9750 2010-05-17 21:32:11 +0000 Why may a content-type handler that isn't a plugin not handle a resource linked to by <embed>? 2010-10-04 14:29:00 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified All All RESOLVED WONTFIX http://www.whatwg.org/specs/web-apps/current-work/#sandboxPluginEmbed P2 normal --- 1 contributor ian bjartur79 ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 35725 0 contributor 2010-05-17 21:32:11 +0000 Section: http://www.whatwg.org/specs/web-apps/current-work/#sandboxPluginEmbed Comment: Why may a content-type handler that isn't a plugin not handle a resource linked to by <embed>? Posted from: 157.157.197.114 35812 1 bjartur79 2010-05-23 20:46:36 +0000 User agents MUST use a plugin to handle content linked to by the <embed> element. This should be an implementation detail and UAs should be allowed to render the resource <embed> represents outside of the UAs user interface. For example a browser with a TUI may allow users to view a video linked to by an <embed> element outside of its textual interface. 37873 2 ian 2010-08-25 23:05:54 +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: The definition of "plugin" already takes that into account, as far as I can tell.