W3C home > Mailing lists > Public > www-style@w3.org > October 2008

Re: Selectors

From: David Hyatt <hyatt@apple.com>
Date: Thu, 16 Oct 2008 14:23:09 -0500
To: Daniel Glazman <daniel.glazman@disruptive-innovations.com>
Cc: Anne van Kesteren <annevk@opera.com>, "www-style@w3.org" <www-style@w3.org>
Message-id: <6093D268-AD55-48C2-B4BF-EED44C6989FE@apple.com>

It works this way in every browser though.  When every browser works  
the same way, I call that consensus. :)

dave

On Oct 16, 2008, at 2:20 PM, Daniel Glazman wrote:

> David Hyatt wrote:
>> In WebKit, :hover is hierarchical (and effectively DOM-based).  We  
>> determine what element is hit, and then that element and all  
>> ancestors up the DOM tree are considered to be in :hover.  The same  
>> is true for :active.  It doesn't matter if the ancestor doesn't  
>> happen to spatially contain the child (and why should it...  
>> consider wanting to highlight a hierarchical menu when you're  
>> browsing around in a popped up submenu).
>> I honestly do not think we (Apple) can change this behavior.  It's  
>> fundamental to WebKit apps on OS X that our :hover/:active work  
>> this way and has been for years.
>
> Test case attached... Make the pointer hover over the rightmost
> block and see the other one become yellow too. Not surprising
> if you have some DOM knowledge, extremely surprising if you take
> a look at the name of our pseudo-class "hover".
>
> </Daniel>
>
> <hovertest.xhtml>
Received on Thursday, 16 October 2008 19:23:51 GMT

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