Closed Bug 503813 Opened 15 years ago Closed 15 years ago

changing generated content on :hover does not work when the hovering is over the generated content


(Core :: CSS Parsing and Computation, defect, P2)




Tracking Status
status1.9.2 --- beta1-fixed
status1.9.1 --- ?


(Reporter: dev-null, Assigned: roc)



(Keywords: regression, testcase)


(3 files)

Attached file testcase
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2a1pre) Gecko/20090712 Minefield/3.6a1pre

Steps to reproduce:
1. Open the testcase.
2. Mouse over "generated content" at the right of "testA".

Actual result:
Does nothing.

Expected result:
:hover should work like testB, i.e. "generated content" in testA should change to red "content is used with hover".

20080817033619 works fine.
20080818033342 fails.

Likely from bug 238072.
Flags: wanted1.9.1.x?
Flags: blocking1.9.2?
Attached file testcase with <a>
When this bug occurs with <a>, click on the generated content does not work first time.

In this testcase, clicking on "generated content" at the right of "testA" once does nothing.
When click again, it follows the link.
Is this the same bug? Or another separate bug is needed?
Assignee: nobody → roc
Flags: blocking1.9.2? → blocking1.9.2+
Priority: -- → P2
status1.9.1: --- → ?
Flags: wanted1.9.1.x?
Summary: :hover does not work with generated content → changing generated content on :hover does not work when the hovering is over the generated content
OS: Windows XP → All
Hardware: x86 → All
Attached patch fixSplinter Review
GetContentForEvent should return the nearest enclosing non-generated content.

This function is used in quite a few places but I'm pretty sure this is the right thing to do in all those cases. We simply shouldn't be targeting DOM events at  generated content.
Attachment #397605 - Flags: review?(dbaron)
This patch fixes both testcases in this bug.
Whiteboard: [needs review]
Comment on attachment 397605 [details] [diff] [review]


But I think you should also remove nsHTMLCanvasFrame::GetContentForEvent; it's now the only GetContentForEvent implementation that doesn't do this fixup, and as far as I can tell it's entirely unneeded.  (I can't see how it can occur in generated content now, but we may as well avoid problems if it ever can.)
Attachment #397605 - Flags: review?(dbaron) → review+
Whiteboard: [needs review] → [needs landing]
Closed: 15 years ago
Flags: in-testsuite+
Resolution: --- → FIXED
Whiteboard: [needs landing] → [needs 1.9.2 landing]
Whiteboard: [needs 1.9.2 landing] → [needs 192 landing]
Wed Sep 02 14:46:33 2009 +1200 (at Wed Sep 02 14:46:33 2009 +1200):
Whiteboard: [needs 192 landing]
Confirmed fixed in 1.9.2.
You need to log in before you can comment on or make changes to this bug.