W3C home > Mailing lists > Public > www-style@w3.org > May 2003

Re: Control an element that is not child of the trigger

From: Andy <aholmes84@shaw.ca>
Date: Wed, 14 May 2003 11:34:09 -0700
To: Hakon G <hakon_@everyday.com>, www-style@w3.org
Message-id: <3EC28C21.7040802@shaw.ca>



Hakon G wrote:

> Would it really severe the rendering time that much?
> This feature would only make sense to use with user-interaction 
> pseudo-classes like :hover :active and :focus.
> Therefore I fail to see how they should do anything to the page-load 
> process, since it's unlikely that there will be such a trigger before 
> the page has loaded.
>
> About the  sign - yeah I only meant that I chose to use it in the 
> example, nothing more than that. It could be any character.
>
> Yes, I checked those pages but I guess they couldn't do the job in 
> this desireable case: to get a table-row to change background-color 
> when there's a checkbox on it checked.
>
>
> check here
> ...
> ...
>
>
> How about an operator like this which would give the reverse effect of >
>
> input[type="checkbox"][checked] < tr { background-color: red }
> tr { background-color: grey }
>
> When the checkbox is checked, the tr will change color.
> That shows another problem. I don't know how to assign a subject that 
> is NOT checked. Since in html4, it is a standalone attribute 
> `checked`. But I guess that will be doable with css3 and the pseudo-class.


Hmm, a selector like this would certainly remove a lot of need for 
javascript in certain cases (think dynamic menus), but is this really 
the job of CSS3? I would like to see more discussion on this however.

-Andy
Received on Wednesday, 14 May 2003 14:38:10 GMT

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