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

Re: Selectors

From: Daniel Glazman <daniel.glazman@disruptive-innovations.com>
Date: Thu, 16 Oct 2008 21:20:44 +0200
Message-ID: <48F7940C.3000304@disruptive-innovations.com>
To: David Hyatt <hyatt@apple.com>
Cc: Anne van Kesteren <annevk@opera.com>, "www-style@w3.org" <www-style@w3.org>
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".


Received on Thursday, 16 October 2008 19:21:19 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:27:40 UTC