W3C home > Mailing lists > Public > www-style@w3.org > August 2002

CSS2.1: Unresolved Table Issues

From: fantasai <fantasai@escape.com>
Date: Tue, 20 Aug 2002 07:52:33 -0400
Message-ID: <3D622D81.CD36AC63@escape.com>
To: www-style@w3.org

Over-constrained Table Rows
---------------------------

  If a table row is over-constrained (all widths, paddings, and
  borders are specified, including the table width), what gives?
  There's no margin on the table cells.

  CSS2.1 Section: 17
      References: [1]

Wording Error on Border Conflict Resolution
-------------------------------------------

  | 3.If none of the styles is 'hidden' and at least one of them is
  |   not 'none', then narrow borders are discarded in favor of wider
  |   ones. If several have the same 'border-width' than styles are
  |   preferred in this order: 'double', 'solid', 'dashed', 'dotted',
  |   'ridge', 'outset', 'groove', and the lowest: 'inset'.

  Should probably read "If none of the styles are 'hidden' and at
  least two of them are not 'none'".

  Also, it should be "If several ... then styles are", not "If several
  ... than styles are". 

  CSS2.1 Section: 17.6.2
      References: [1]

Missing Case for Border Conflict Resolution
-------------------------------------------

  | 4. If border styles differ only in color, then a style set on a
  |    cell wins over one on a row, which wins over a row group, column,
  |    column group and, lastly, table.

  What happens if the border styles are both set on individual cells?

  CSS2.1 Section: 17.6.2
      References: [1]

Unnecessary Auto-Layout?
------------------------

  | Fixed table layout
  |
  | ...
  |
  | The table's width may be specified explicitly with the 'width'
  | property. A value of 'auto' (for both 'display: table' and
  | 'display: inline-table') means use the automatic table layout
  | algorithm. 

  If neither margin is 'auto', then the width can be calculated
  and the fixed table layout algorithm easily invoked. Auto layout
  is the default--if the author explicitly chose the fixed layout
  algorithm, then why should "width: auto" revert it to automatic?

  Taking out this clause also provides a mechanism for "making
  tables automatically fit their containing blocks" without waiting
  for "future versions of CSS" to introduce new properties.

  CSS2.1 Section: 17.6.2
      References: [2]

Ambiguous Table Backgrounds
---------------------------

  Too long and complicated to repeat here. See [3]

  CSS2.1 Section: 17
      References: [3]

-----------
[1] fantasai. "border-collapse conflicts and other topics", www-style@w3.org
     (2000-07-17).
     message-id: <3973C761.C2627DB2@escape.com>
     http://lists.w3.org/Archives/Public/www-style/2000Jul/0011.html
[2] Syreeni, Sampo. "css2 table width calculation", www-style@w3.org (2000-12-03).
      message-id: <Pine.SOL.4.30.0012031710540.18011-100000@kruuna.Helsinki.FI>
      http://lists.w3.org/Archives/Public/www-style/2000Dec/0015.html
[3] fantasai. "Table Backgrounds", www-style@w3.org (2002-05-11).
      message-id: <3CDD7CCC.1AC14609@escape.com>
      http://lists.w3.org/Archives/Public/www-style/2002May/0077.html
Received on Tuesday, 20 August 2002 07:48:36 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 13:54:15 GMT