W3C home > Mailing lists > Public > www-style@w3.org > September 2006

Re: [css3-selectors] :parent selector

From: David Woolley <david@djwhome.demon.co.uk>
Date: Mon, 25 Sep 2006 21:27:01 +0100 (BST)
Message-Id: <200609252027.k8PKR1M01102@djwhome.demon.co.uk>
To: www-style@w3.org

> > What happens if the relevant child is a several mega bytes down a
> > streamed document?  In particular, what happens if it changes the
> > display mode, in particular to none.
> 
> Answer: If you are asking what happens if child:parent is set to  
> display:none, then the answer is that the parent disappears. Why would  
> this be a problem?

The parent and all its children disappear, after the user has read some
of them.

My particular concern though, was whether or not the special behaviour
of display: none is clearly enough documented to avoid any possibility
of this resulting in a loop, and whether or not it was clear enough 
as to what to do is a later rule, matched by a later child, cancelled
the display: none.
Received on Monday, 25 September 2006 20:28:36 GMT

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