1706066 - Calling setRDMPaneMaxTouchPoints does not set the orientation on iframes

Status: RESOLVED FIXED

(DevTools :: Responsive Design Mode, defect, P2)

Description

[Nicolas Chevobbe [:nchevobbe]]

Steps to reproduce

1. Go to https://firefox-rdm-max-touch-points.glitch.me/
2. Enable RDM
3. Hit the "enable touch simulation" button

Expected results

The input value is constantly updated and is set to the value of navigator.maxTouchPoints.
The 2 inputs should always have the same value as we simulate touch simulation.

Actual results

The input in the iframe is never changed, it's always 0.
This does not rely on Fission at all (the iframe in the demo page is on the same origin, setting a different origin results in the same broken behaviour).

---

Looks similar to Bug 1704830

Comment 1

[Alexandra Borovova [:Sasha]]

Attachment: Bug 1706066 - Always use maxTouchPointsOverride for top level browsing context.

Comment 2

[Alexandra Borovova [:Sasha]]

Attachment: Bug 1706066 - [devtools] Extend mochitests to checks for maxTouchPoints in a iframe.

Comment 3

[Pulsebot]

Pushed by [e-mail]:
https://github.com/mozilla-firefox/firefox/commit/9700371b499e
https://hg.mozilla.org/integration/autoland/rev/52513e535046
Always use maxTouchPointsOverride for top level browsing context. r=dom-core,smaug
https://github.com/mozilla-firefox/firefox/commit/975653d57082
https://hg.mozilla.org/integration/autoland/rev/3e162552821f
[devtools] Extend mochitests to checks for maxTouchPoints in a iframe. r=devtools-reviewers,nchevobbe

Comment 4

[Cosmin Sabou [:CosminS]]

https://hg.mozilla.org/mozilla-central/rev/52513e535046
https://hg.mozilla.org/mozilla-central/rev/3e162552821f