html.onmouseleave fired on mouseover of the input warning tip

NEW
Unassigned

Status

()

Firefox
General
4 years ago
4 years ago

People

(Reporter: Dron Rathore, Unassigned)

Tracking

({testcase})

33 Branch
x86
All
testcase
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

4 years ago
Created attachment 8451507 [details]
test.html

STR:

1: Open the attachment
2 [review]: Enter an invalid email
3: Click submit
4: Mouseover the Info Tip of the input box.
5: The "html".onmouseleave event is been fired!

Expected result: Event shouldn't be fired.
The info tip of input box must belong to the document itself. Try the same file in Chrome and see the results.
(Reporter)

Comment 1

4 years ago
I think the Element that's been created belongs to the global XUL and not to the document.
(Reporter)

Updated

4 years ago
Summary: window.onmouseout fired on mouseover of the input warning tip → html.onmouseout fired on mouseover of the input warning tip
(Reporter)

Updated

4 years ago
Summary: html.onmouseout fired on mouseover of the input warning tip → html.onmouseleave fired on mouseover of the input warning tip

Comment 2

4 years ago
If the element being shown is inside the document, that would mean it's detectable by the document and shows up in the DOM. AFAICT it doesn't, even in Chrome. I rather expect they just ignore mouse events on the panel...

Dolske, can we make the panel mousethrough="always", or do we think being able to select text in the panel is more important?
Flags: needinfo?(dolske)
Keywords: testcase

Updated

4 years ago
Blocks: 561636
Why is this a bug? Seems like reasonable (even outright _expected_) behavior to me. It's no different than mousing over any other arrow panel in the UI (eg, click the site identity button, and the testcase does the same thing).
Flags: needinfo?(dolske)
(Reporter)

Comment 4

4 years ago
My point is, the arrow panels that are created for UI elements inside a DOM[HTML] must follow this rule i.e. The event must not have been fired. The Site identity button arrow panel doesn't belong to DOM so must not follow it also any other addon arrow panel too.
You need to log in before you can comment on or make changes to this bug.