9658 2010-05-05 04:04:25 +0000 Define (correctly) how object, ins, del, map, button affects outlines 2010-10-04 14:46:39 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified All All RESOLVED WONTFIX http://dev.w3.org/html5/spec/text-level-semantics.html#the-object-element P2 normal LC 9657 1 xn--mlform-iua ian ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 35442 0 xn--mlform-iua 2010-05-05 04:04:25 +0000 Neither "object", "ins", "del", "map" nore "button" are defined as 'sectioning root' or 'sectioning content' elements. Instead, they are defined as having a transparent content model. My suspicion is that it is because they are defined as having a transparent content model, that it isn't defined how they take part in outlines. I'l list the specific elements in question. OBJECT ----- If you for example have a document <body> like this: <body> <h1>Foo</h1> <p>…</p> <object type=image/gif data=image> <section> <h2>Bar</h2> <p>…</p> </section> </object> <h3>Bas</h3> <p>…</p> </body> then the outlining algorithm would, as I gather, see a document with 3 headings, where the <h2> would be the outline "child" of <h1>, despite that <h2> is child of <object>. And likewise, <h3> would be the child of <h2>, despite that one is inside and the other is outside <object>: |-H1:Foo |--H2:Bar |---H3:Bas The logical thing is that the content of <object> creates its own outline, independent from the "global" outline of the document. Only those that read the fallback will perceive it. Also, if <object> is used like <iframe>, to embed an external HTML document, then the outline of the external document also creates its own outline. |-H1:Foo |<object> | H2:Bar |</object> |-- H3:Bas BUTTON ------- The <button> element should be treated much like the mark-up fallback of <object> - it shoudl build its own independent outline. MAP --- Firstly, if <map> occurs inside <object>, then the outline problem must eventually "happen" inside <object>. But, secondly, in general, it seems most logical to me to treat it the content of <map> as if it builds its own outline, also when it occurs outside <object>. Because <map> is kind of like the fallback text of an image also when it it is situated outside the <object>. So, for example, if a <map> contains a <h2> element, then this element should probably not take part in the over all outline of the document. INS & DEL ------- INS .... <ins> represents content which is part of the document. Thus it should no doubt take part in the algorithm. DEL .... <del> represents content which has been removed from the document. Thus it does not seem logical that content inside <del> contribute to the over all outline of a document. OTOH, it could seem logical if one was able to switch between seeing the outline with <ins> and with <del>. (In other words: there are many possibilities when it comes to <ins> and <del>. One could also imagine outlines based on INS or DEL with the same date stamps in the datetime attirbute etcs. ) Reference: the A elemenet -------------------- Just for reference, I mention <a>, which is also transparent. <a> should of course take part in the over all outline of the document. I mention it here to show how it is wrong to juxtapose <object> and <a> - they should have diffefent outline effects. (And thus also have different content models - bug 9657.) 37523 1 ian 2010-08-16 22:26:55 +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: Your understanding of the algorithm is wrong. <object> works just like <div>. Please file other issues in their own bugs.