18091 2012-07-18 17:14:50 +0000 embed and object should match a, del, ins, and map 2012-10-12 22:04:04 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified Other other RESOLVED WORKSFORME http://www.whatwg.org/specs/web-apps/current-work/#phrasing-content-0 P3 normal --- 1 contributor eoconnor eoconnor mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 70650 0 contributor 2012-07-18 17:14:50 +0000 This was was cloned from bug 16381 as part of operation convergence. Originally filed: 2012-03-14 21:52:00 +0000 ================================================================================ #0 contributor@whatwg.org 2012-03-14 21:52:07 +0000 -------------------------------------------------------------------------------- Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/elements.html Multipage: http://www.whatwg.org/C#phrasing-content-0 Complete: http://www.whatwg.org/c#phrasing-content-0 Comment: embed and object should match a, del, ins, and map Posted from: 17.212.152.28 User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_3) AppleWebKit/536.3 (KHTML, like Gecko) Version/5.2 Safari/536.3 ================================================================================ #1 Edward O'Connor 2012-03-14 21:54:13 +0000 -------------------------------------------------------------------------------- a, del, embed, ins, map, and object all have a transparent content model, and so they should all be considered phrasing content only when they contain phrasing content. This is made explicit in this section for a, del, ins, and map. Please update the entries for embed and object to match. ================================================================================ 76181 1 eoconnor 2012-10-12 22:04:04 +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: Accepted Change Description: N/A Rationale: The way content models are specced has changed; the problem identified is no longer present in the spec.