G K Reporter
	Description • 20 years ago

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.1.4322)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3

On the example page http://moz.gknutzen.com/activeVhover.html, in firefox, the 
behavior of the parent class ("xxx")is inconsistent when a child class is in 
the :active or :hover state.

The parent element is responding to the child's :hover state but not to the 
child's :active state. 

According to http://www.w3.org/TR/CSS21/selector.html#dynamic-pseudo-classes
"CSS 2.1 doesn't define if the parent of an element that is ':active' 
or ':hover' is also in that state."

Currently, we have it both ways.

I have tried to find a reference to this situation elsewhere and have found 
nothing.


Reproducible: Always

Steps to Reproduce:
To see this in action, mouse over and click "Unspanned". Notice the background 
color changes from dark red, to medium red, to light red as is expected. Also 
note that the background of the child span element "Spanned" changes from aqua 
to yellow to green as is expected.

Now mouse over and click "Spanned". Notice the background changes from aqua to 
yellow to green as expected. But notice that the background of the parent 
element "Unspanned" changes from dark red to medium red but not to light red.


Actual Results:  
The parent element is responding to the child's :hover state but not to the 
child's :active state. 


Expected Results:  
My thought is that the parent should repsond both to the :active state as well 
as the :hover state. It is my expected behavior in this situation. I have also 
found no work around.


Possibly in play here is the fact that the child element "Spanned" does not 
seem to be inheriting the properties of the parent link. Example, the words are 
not underlined. I am unsure if this is a separate bug, part of this one or by 
design.

	David Baron :dbaron: Assignee
	Comment 1 • 20 years ago

This has been fixed on the trunk for a long time (you're using a build from the
1.7 branch).

*** This bug has been marked as a duplicate of 65917 ***