- From: Gérard Talbot <www-style@gtalbot.org>
- Date: Mon, 07 Mar 2016 18:38:59 -0500
- To: Greg Whitworth <gwhit@microsoft.com>
- Cc: Francois Remy <frremy@microsoft.com>, W3C www-style mailing list <www-style@w3.org>
Le 2016-03-07 11:15, Greg Whitworth a écrit : [snipped] > until we had a > specification that filled in all of the "undefined" sections of the > 2.1 spec More than 10 years ago, I wrote that CSS3 modules must (or should?) specify, must try to resolve all of the instances of "is undefined", "can not define", "can not be defined", "free to guess", "free to make a guess" occurences found in CSS2.1. Some areas or some sentences of CSS2.1, section 17 Tables https://www.w3.org/TR/2011/REC-CSS2-20110607/tables.html are, in my opinion, difficult or very difficult to understand. Tables are over-specified in current specs; therefore, there will be logical contradictions happening. [snipped] > as > much as we want to say 2+2=4; the web unfortunately is, at times, > depending on it equaling 5, and others 6000 (see width and height > calculation and unit resolution as an example of this). Greg, I am not sure I understand what you mean with your "others 6000 (see width and height calculation and unit resolution as an example of this)" [snipped] > here is the process > that Francois and I have been taking: > * Find a hole in the spec > * Write a bunch of tests and test them in Firefox, Chrome, Safari and > Microsoft Edge to see what the various browsers do (these will > ultimately become some of our tests for REC) > * If there is consensus document that as the standard > * If there is not consensus but the majority match, make this the > standard > * If there is an even split, document the one that makes the most > sense and get working group consensus [snipped] > [1] > https://blogs.windows.com/msedgedev/2016/01/21/microsoft-edge-2015-in-review/ > [2] > https://bugs.chromium.org/p/chromium/issues/detail?id=465419&can=1&q=gwhit%40microsoft.com&colspec=ID > Pri M Stars ReleaseBlock Component Status Owner Summary OS Modified# > [3] https://drafts.csswg.org/css-tables-3/#bug-list In your bug list: Table [wrapper!] boxes should be wide enough to contain the caption: *_this has been already resolved as far as I can say_* http://www.gtalbot.org/BrowserBugsSection/css21testsuite/horizontal-layout-table-vs-caption-boxes-1.html http://www.gtalbot.org/BrowserBugsSection/css21testsuite/caption-100pct-width-001.xht http://lists.w3.org/Archives/Public/www-style/2010Sep/0186.html http://test.csswg.org/suites/css2.1/nightly-unstable/html4/anonymous-table-box-width-001.htm https://wiki.csswg.org/spec/css2.1#issue-172 When caption is wider than table box (not the table wrapper box): Expected: _____________________________________ | CAPTION CAPTION CAPTION CAPTION | ------------------------------------- | +-----+-----+-----+ | | | | | | | | +-----+-----+-----+ | | | | | | | | +-----+-----+-----+ | |___________________________________| Actual in some browsers: _______________________ | CAPTION CAPTION CAPTION CAPTION ----------------------- | +-----+-----+-----+ | | | | | | | | +-----+-----+-----+ | | | | | | | | +-----+-----+-----+ | |_____________________| - - - - - The spec should answer the tough questions (involving rowspanning cells and 'border-collapse: collapse') raised by Mitz: https://bugs.webkit.org/show_bug.cgi?id=8735#c7 - - - - - " table-row-group (In HTML: TBODY) Specifies that an element groups one or more rows. " 2.1. Table Structure https://drafts.csswg.org/css-tables-3/#table-structure This would have to be changed (and should be changed) into: Specifies that an element groups zero or more rows. HTML4 said 1 or more. HTML5 says 0 or more. Search for "Chris Rebert" and "empty <tbody>" for this. [CSS21][CSS22][css-tables][css3-tables] Table sanity/regression testcase needs review http://lists.w3.org/Archives/Public/www-style/2015Jul/0392.html - - - - - - "Value: normal | fixed Initial: separate " 3.4.1. The Table-Layout property https://drafts.csswg.org/css-tables-3/#table-layout-property It is now "Value: auto | fixed Initial: auto " https://www.w3.org/TR/CSS21/tables.html#propdef-table-layout so, this must be 2 errors. - - - - - - 2.4. Spanning We should define how spanning works. https://drafts.csswg.org/css-tables-3/#spanning Quick rowspanning test (with minimal code): http://www.gtalbot.org/BrowserBugsSection/css21testsuite/rowspanning-cell-challenge-001.html Expected result (approximate table layout): +-----------+-----------+ | |C | |A +-----------+ | | | | |D | +-----------+ | |B | | +-----------+-----------+ Actual result (approximate table layout) in many browsers (Firefox 44, Opera 12.16, IE11) (don't know about Edge14) +-----------+-----------+ | | | |A |C | | | | +-----------------------+ | | | |B |D | | | | +-----------------------+ Whether 'table-layout: fixed' is declared or not makes no difference. Gérard
Received on Monday, 7 March 2016 23:39:32 UTC