mouseenter/mouseleave fire differently on <select>s in e10s mode.

NEW
Assigned to

Status

()

Core
DOM: Events
P3
normal
a year ago
a month ago

People

(Reporter: Thomas Wisniewski, Assigned: mconley)

Tracking

(Blocks: 1 bug)

Trunk
Points:
---

Firefox Tracking Flags

(firefox54 affected)

Details

(Whiteboard: [webcompat], URL)

MozReview Requests

()

Submitter Diff Changes Open Issues Last Updated
Loading...
Error loading review requests:

Attachments

(3 attachments)

(Reporter)

Description

a year ago
It seems that <select>s and their dropdowns are considered separate objects in e10s mode, for the purposes of determining when to fire mouseenter/mouseleave events. In a non-e10s window the <select> *and* its dropdown are both counted as one object.

You can see this in effect in the attached testcase by comparing when the events are fired between an e10s and non-e10s window.

This is breaking the quality menu option on clips.twitch.com as per the given URL (as reported in webcompat.com issue #4697).
(Reporter)

Comment 1

a year ago
Created attachment 8841106 [details]
testcase.html

Just attaching the aforementioned test-case.
Mike is probably in the best position to fix or investigate this.
Flags: needinfo?(mconley)
I'll try to look at this this week.
Assignee: nobody → mconley
Flags: needinfo?(mconley)
Comment hidden (mozreview-request)
Comment hidden (mozreview-request)
Attachment #8845638 - Flags: review?(enndeakin)
Duplicate of this bug: 1396596
Blocks: 1154677
Priority: -- → P3
HsinYi, is it something your team can keep it up and running?
Flags: needinfo?(htsai)
Ben, please help this after another similar (?) bug 1296264. Thanks.
Flags: needinfo?(htsai) → needinfo?(btian)
Blocks: 1409645
No longer blocks: 1154677

Updated

a month ago
Flags: needinfo?(ben.tian)
You need to log in before you can comment on or make changes to this bug.