Closed
Bug 1606061
Opened 4 years ago
Closed 4 years ago
[Fission] Make nsDocShell::SetTouchEventsOverride Fission compatible
Categories
(Core :: DOM: Navigation, defect, P1)
Core
DOM: Navigation
Tracking
()
Tracking | Status | |
---|---|---|
firefox84 | --- | fixed |
People
(Reporter: whimboo, Assigned: smacleod)
References
Details
Attachments
(1 file)
Similar to bug 1605243 using docShell.setTouchEventsOverride
turns out to be not Fission compatible because it iterates over the child list:
Comment 3•4 years ago
|
||
Nika said this can be added to BrowsingContext fields.
Assignee: nobody → smacleod
Status: NEW → ASSIGNED
Updated•4 years ago
|
Priority: P3 → P2
Updated•4 years ago
|
Priority: P2 → P1
Assignee | ||
Comment 4•4 years ago
|
||
This change removes docshell's mTouchEventsOverride
and replaces it
with a new BrowsingContext
field TouchEventsOverrideInternal
.
All uses of the old field have been replaced and an override should
now work under fission when there are cross-origin descendent frames.
Bug 1606061 - move usage of TouchEventsOverride to BrowsingContext.
Pushed by smacleod@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/98f9ddb69629 move TouchEventsOverride to BrowsingContext. r=farre,devtools-backward-compat-reviewers
Comment 6•4 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
status-firefox84:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 84 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•