Closed
Bug 1704737
Opened 3 years ago
Closed 3 years ago
Call BrowsingContext#setRDMPaneMaxTouchPoints in the parent process
Categories
(DevTools :: Responsive Design Mode, task)
DevTools
Responsive Design Mode
Tracking
(Fission Milestone:M7a, firefox90 fixed)
| Tracking | Status | |
|---|---|---|
| firefox90 | --- | fixed |
People
(Reporter: nchevobbe, Assigned: nchevobbe)
References
(Blocks 1 open bug)
Details
(Whiteboard: dt-fission-m3-mvp)
Attachments
(1 file)
No description provided.
|
Assignee | |
Updated•3 years ago
|
|
|
Assignee | |
Updated•3 years ago
|
Whiteboard: dt-fission-m3-mvp
|
||
Updated•3 years ago
|
Fission Milestone: --- → M8
|
|
Assignee | |
Updated•3 years ago
|
Summary: Set setRDMPaneMaxTouchPoints BrowsingContext property in the parent process → Call BrowsingContext#setRDMPaneMaxTouchPoints in the parent process
|
|
Assignee | |
Comment 1•3 years ago
|
||
This removes the setMaxTouchPoints methods from the ResponsiveActor
and instead puts a rdmPaneMaxTouchPoints configuration that will
be handled in the parent process.
browser_max_touchpoints.js is expanded to add more test cases to make
sure we cover different scenarios.
We don't check the property in the iframe as it does not work at the moment,
and Bug 1706066 was filed to fix this.
Depends on D112149
|
||
Updated•3 years ago
|
Assignee: nobody → nchevobbe
Status: NEW → ASSIGNED
Pushed by nchevobbe@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/fab1bb3a111a [devtools] Call BrowsingContext#setRDMPaneMaxTouchPoints in the parent process. r=ochameau,devtools-backward-compat-reviewers.
|
||
Comment 3•3 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
status-firefox90:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 90 Branch
|
|
||
Updated•3 years ago
|
Fission Milestone: M8 → M7a
You need to log in
before you can comment on or make changes to this bug.
Description
•