W3C home > Mailing lists > Public > www-style@w3.org > December 2009

Re: Request for ::di pseudoelement

From: Brad Kemper <brad.kemper@gmail.com>
Date: Fri, 18 Dec 2009 17:51:46 -0800
Message-Id: <4F69CA95-DAEB-4D19-9096-3A616C50896F@gmail.com>
To: Brad Kemper <brad.kemper@gmail.com>
Cc: "Tab Atkins Jr." <jackalmage@gmail.com>, www-style list <www-style@w3.org>

On Dec 18, 2009, at 5:33 PM, Brad Kemper <brad.kemper@gmail.com> wrote:

> On Dec 18, 2009, at 5:09 PM, "Tab Atkins Jr." <jackalmage@gmail.com>  
> wrote:
>> On Fri, Dec 18, 2009 at 6:33 PM, Brad Kemper  
>> <brad.kemper@gmail.com> wrote:
>>> On Dec 18, 2009, at 3:18 PM, "Tab Atkins Jr."  
>>> <jackalmage@gmail.com> wrote:
>>>> It's possible that this can have its definition generalized  
>>>> somewhat
>>>> so it makes sense outside of this specific use-case.
>>> Maybe "Presentation Levels" could be wrangled into doing that? Or  
>>> is that
>>> spec actually "specifiction" (my new favorite word)?
>> Hmm, I'm not seeing an immediate connection here.  What were you  
>> thinking of?
> Well, I think I am misunderstanding how Presentation Levels work.   
> When I first read it, I was thinking that they could group elements  
> by defining their level, and then select that group to style as a  
> unit (ie, with an anonymous box around contiguous elements of the  
> same level), but now I think that I totally read too much into it.  
> So... Sorry for the noise.

The thing that made me think of this was that I was thinking "what  
else besides definition list might have a logical relationship, but  
not necessarily an existing element encapsulating them?" and I  
immediately thought of a heading level and the paragraphs that  
followed it before another heading was encountered. And that made me  
think of Presentation Levels. 
Received on Saturday, 19 December 2009 01:53:30 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:07:41 UTC