- From: L. David Baron <dbaron@dbaron.org>
- Date: Mon, 6 Apr 2009 10:51:27 -0700
- To: www-style@w3.org
On Monday 2009-04-06 10:27 -0700, Brad Kemper wrote: > Border is a special case as part of the unique conflict resolution that > substitutes for getting the values from inheritance (with no such > complicated inheritance-free value-passing methods being part of normal > CSS). In theory, I don't see why a similar conflict resolution (namely > step 4) could not be used for 'color' and 'text-align'. Because: (1) Border is a non-inherited property, so the end result of the CSS cascading and inheritance algorithm still leaves you with information about where it was specified (2) The default for border-style is 'none' (which is a result of being non-inherited), so there's a concept of "not having a border" that allows useful fallback. border conflict resolution can happen without messing with the internals of CSS cascading and inheritance. To do the same for an inherited property like 'color' or 'text-align' requires messing with the guts of the cascading and inheritance rules (and making them a LOT more complicated). It would be much simpler to solve these problems with :col() and :nth-col(); is there a good enough reason to prefer a significantly more complicated solution? -David -- L. David Baron http://dbaron.org/ Mozilla Corporation http://www.mozilla.com/
Received on Monday, 6 April 2009 17:52:05 UTC