W3C home > Mailing lists > Public > www-style@w3.org > July 2010

Re: Pseudo-selector for virtual elements

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Fri, 16 Jul 2010 09:05:32 -0700
Message-ID: <AANLkTimzaT4KI1UdEvsSHQLxRLhdlpZEASq-OaxuzG27@mail.gmail.com>
To: Eduard Pascual <herenvardo@gmail.com>
Cc: Andrés Sanhueza <peroyomaslists@gmail.com>, www-style@w3.org
On Fri, Jul 16, 2010 at 8:51 AM, Eduard Pascual <herenvardo@gmail.com> wrote:
> On Fri, Jul 16, 2010 at 4:03 AM, Andrés Sanhueza
> <peroyomaslists@gmail.com> wrote:
>> 2010/7/12 Eduard Pascual <herenvardo@gmail.com>:
>>> On Sun, Jul 11, 2010 at 7:27 PM, Tab Atkins Jr. <jackalmage@gmail.com> wrote:
>>
>>> In any case, now I am even more convinced that a request for a CSS
>>> feature to work-around the mark-up's inability to describe a structure
>>> is quite a symptom of a flaw on the mark-up language. In other words,
>>> the use cases should be addressed by HTML through explicit structuring
>>> elements.
>>
>> I agree, but there are cases where it is justified, like if I want to
>> group several <li> in a list for showing something like a table where
>> an actual table isn't appropriate (like an image gallery). If I
>> instead do something like this:
>>
>> <ul>
>> <ligroup>
>> <li></li>
>> <li></li>
>> <li></li>
>> </ligroup>
>> <ligroup>
>> <li></li>
>> <li></li>
>> <li></li>
>> </ligroup>
>> <ligroup>
>> <li></li>
>> <li></li>
>> </ligroup>
>> </ul>
>>
>> I'm using the grouping element merely for presentational purposes—as
>> in dividing a row of each one and keeping three columns, so a CSS
>> workaround is desirable.
>>
>
> Aren't CSS Grid Positioning [1] and display:table-* [2] supposed to
> address those "looks like a table but is not tabular data" cases?

Yes, but neither one addresses the "split up a linear set of elements
into rows of a table" case.  At least, not yet.

~TJ
Received on Friday, 16 July 2010 16:06:25 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:29 GMT