12322 2011-03-17 01:25:37 +0000 [Polyglot] "Required Elements" - clarify use of <colgroup> and more. 2011-08-04 05:07:43 +0000 1 1 1 Unclassified HTML WG LC1 HTML/XHTML Compatibility Authoring Guide (ed: Eliot Graff) unspecified PC All CLOSED FIXED http://dev.w3.org/html5/html-xhtml-author-guide/html-xhtml-authoring-guide.html#required-elements P2 normal --- 1 xn--mlform-iua eliotgra eliotgra mike public-html-admin public-html-wg-issue-tracking xn--mlform-iua public-html-bugzilla oldest_to_newest 46767 0 xn--mlform-iua 2011-03-17 01:25:37 +0000 The Polyglot Markup spec can easily be read to say that <colgroup> is obligatory in any table: ]] Polyglot markup explicitly uses a colgroup element surrounding groups of col elements within a table element. HTML parsers insert the colgroup element, but XML parsers do not, thus creating different DOMs. [[ At least, I did. I even created this Live DOM viewer test to show that it is not the case: http://tinyurl.com/colgroup What you wanted to say was that <colgroup> is an obligatory wrapper aroun any <col>. The confusing wordings are "uses", "explicit" and "insert". Perhaps the word "code" could been used somewhere? The wording should also imply clear that it can be more than one colgroup in the same table. I suggest this: ]] In the code of polyglot markup, a col element always has to occur wrapped inside a colgroup element. In HTML, if in the code a group of one or more adjacent col elements are not explicitly wrapped inside a colgroup element, then the parser will create a new colgroup element and wrap around them. XML parsers will not do the same thing, thus creating different DOMs.[[ In the same go, place also fix the text about <tbody>. You should say that authors must use either tbody, thead or tfoot. I suggest this: ]] In the code of polyglot markup, a tr element always has to occur wrapped inside a tbody, thead or tfoot element. In HTML, if in the code a group of one or more adjacent tr elements are not explictly wrapped inside a tbody, thead or tfoot element, then the parser will create a new tbody element and wrap around them. XML parsers will not do the same thing, thus creating different DOMs.[[ Another thing: the minimal document example, you have this <html> start tag: <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"> Please EITHER clarify that you mean a minimal ENGLISH document. OR replace lang="en" xml:lang="en" with empty attributes (which per HTML5 and XML means that no language has been set): <html xmlns="http://www.w3.org/1999/xhtml" lang="" xml:lang=""> (We discussed another place that ther should always be a lang/xml:lang attribute, so it is OK for me to include the lang/xml:lang attributes.) 46827 1 eliotgra 2011-03-18 22:57:22 +0000 This is a great catch! I've changed the paragraphs in Section 6.1 to the following: ]] Whenever it uses a tr element, polyglot markup always wraps the tr element inside a tbody, thead, or tfoot element. In HTML, if a group of one or more adjacent tr elements are not explictly wrapped inside a tbody, thead, or tfoot element, the HTML parser creates and wraps a new tbody element around the tr elements. XML parsers do not crete the tbody element, thus offering the potential for creating different DOMs. [[ and ]] Whenever it uses col elements within a table element, polyglot markup explicitly uses a colgroup element surrounding groups of the col elements. In HTML, if a group of one or more adjacent col elements are not explicitly wrapped inside a colgroup element, the HTML parser creates and wraps a new colgroup element around the col elements. XML parsers do not create the colgroup element, thus offering the potential for creating different DOMs. [[ Thanks, Eliot 46828 2 xn--mlform-iua 2011-03-18 23:22:54 +0000 Perfect! Except that you wrote "crete" instead of "create" in first paragraph. So, I guess I must open this bug again, because otherwise you would of course never fix it. ;-) 46829 3 eliotgra 2011-03-18 23:27:22 +0000 Ah, you know my work habits! ;-) Fixed. Thanks. E 46830 4 xn--mlform-iua 2011-03-18 23:34:17 +0000 Super. 53184 5 mike 2011-08-04 05:07:24 +0000 mass-move component to LC1 53212 6 mike 2011-08-04 05:07:43 +0000 mass-move component to LC1