45822 - [ESM/CSS]only one node at a time matches :hover

Status: VERIFIED DUPLICATE of bug 5693

(Core :: DOM: UI Events & Focus Handling, defect, P3)

Description

[fantasai]

Overview:

	The :hover triggers only when the cursor is over an elements border or 
	padding. It does not trigger on the content area. And it does not 
	trigger /at all/ on a block.

	HOWEVER! It triggers on the content of a hypertext _link_. ?!?

Steps to Reproduce:

	Open up testcase in Mozilla. View the display, and view the source.

Actual Results:

	See Overview.

Expected Results:

	:hover should trigger on content areas of inlines as well.
	:hover should also trigger on the padding & content of a block-level 
	element.

Tested on Mozilla nightly build (id: 2000071708, 2000071810) on Windows 2000.

Additional comments:

	This seems too obvious not to be a duplicate. I ran a search, came up 
	with nothing, downloaded today's build, retested, and am now doubting 
	the validity of my testcase code. v_v;;;

Comment 1

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

Where's the testcase?  Possibly related bugs (can't tell without the testcase): 
bug 5693, bug 33736, bug 27757, bug 36710

Comment 2

[fantasai]

Stupid me. I forgot to attach it. ^^;;;

Comment 3

[fantasai]

Attachment: testcase

Comment 4

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

I think this is technically a duplicate of bug 5693 / bug 33736 (but don't mark
duplicate without reading the whole paragraph).  The problem is that we only
allow one node at a time to match :hover.  When the mouse is in a text node,
this does not correspond to any element.  However, links are treated specially,
which is why :hover works on links.  Changing to Event Handling and confirming. 
I think we should make this the bug for exactly this issue, since the other two
bugs I mentioned above cover lots of other stuff too.  (However, this issue may
be the only one remaining in bug 33736.)

What we need to do is allow multiple elements at a time to match :hover.  A
:hover selector should match the node in which the mouse is positioned and any
ancestor of that node.

Comment 5

[Hixie (not reading bugmail)]

As per meeting with ChrisD today, taking QA.

Comment 6

[ckritzer (gone)]

This bug has been marked "future" because the original netscape engineer working
on this is over-burdened. If you feel this is an error, that you or another
known resource will be working on this bug,or if it blocks your work in some way
-- please attach your concern to the bug for reconsideration.

Comment 7

[Jerry Baker]

This bug makes it impossible for Web developers to create something resembling 
buttons on their web page with CSS. Everytime the mouse goes over the 
text of a button, the hover state of the button is deactivated. This is 
awkward and encourages the continued use of JS image flips. Mozilla is supposed 
to showcase CSS and its power right? Why is this being held up?

Comment 8

[Tobias Burnus]

Suggest: OS=ALL, Platform=ALL

Comment 9

[Hixie (not reading bugmail)]

fixed

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

Comment 10

[Christine Hoffman]

Verified dup of #5693

Comment 11

[Jerry Baker]

Mass removing self from CC list.

Comment 12

[Jerry Baker]

Now I feel sumb because I have to add back. Sorry for the spam.