- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Tue, 18 Mar 2014 16:22:54 -0700
- To: Brad Kemper <brad.kemper@gmail.com>
- Cc: Viatcheslav Ostapenko <sl.ostapenko@samsung.com>, "robert@ocallahan.org" <robert@ocallahan.org>, Zack Weinberg <zackw@panix.com>, www-style list <www-style@w3.org>
On Tue, Mar 18, 2014 at 4:17 PM, Brad Kemper <brad.kemper@gmail.com> wrote: >> On Mar 17, 2014, at 5:44 PM, "Tab Atkins Jr." <jackalmage@gmail.com> wrote: >>> On Mon, Mar 17, 2014 at 2:46 PM, Brad Kemper <brad.kemper@gmail.com> wrote: >>> What makes it hard? Don't TDs already look to COLs for style resolution? >> >> Only for four specific properties (border, background, width, and >> visibility), which are conceptually styling the *column itself*, not >> the cells in the column. > > Those properties are no more so "column itself" than positioning could be. Yes they are. Columns, themselves, can have borders, backgrounds, widths, and a visibility; these are all taken into account when the whole table is being assembled and painted. > They are still applied to the TD, not some tall rectangle sitting behind it spanning all the rows. And if you can select all the cells in a row and style them, I don't see why you shouldn't be also able to select all the cells in a column and style them. Conceptually it is the same, and technically it doesn't sound all that more difficult. It is. This isn't an arbitrary choice. For example, which cells are in a column is a result of styling, itself, as you can change the 'display' value for individual cells. Further, allowing arbitrary styling on columns to mean "style the cells in the column" means that cells are now inheriting from *two* parents, which requires adjudication of some sort. It's possible that more properties could be applied to the column itself and dealt with at the same time as borders/etc are, but it's definitely not something you can do for arbitrary styles. ~TJ
Received on Tuesday, 18 March 2014 23:23:41 UTC