+++ This bug was initially created as a clone of Bug #1620309 +++ STR 1. Enable apz.allow_zooming and fission.autostart, and restart. 1. Open the attached test case. Note that the toplevel document has origin https://bug16?????.bmoattachments.org and the subframe has origin https://example.com, and so the two documents are loaded into separate processes. 1. Attempt to interact with the example.com subframe (highlight text, scroll, etc). You should notice that this doesn't work. 1. Interact with the toplevel document (highlight text, scroll, etc), and then try to interact with the subframe again. You should notice that this now works as expected. I can reproduce this on Linux and macOS, and cpeterson was able to reproduce on Windows. As far as I can tell, this only reproduces when the toplevel content has `height: 100%; overflow: auto` and the iframe has `position: fixed`.
Bug 1645433 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
+++ This bug was initially created as a clone of Bug #1620309 +++ STR 1. Enable apz.allow_zooming and fission.autostart, and restart. 1. Open the attached test case. Note that the toplevel document has origin https://bug1645433.bmoattachments.org and the subframe has origin https://example.com, and so the two documents are loaded into separate processes. 1. Attempt to interact with the example.com subframe (highlight text, scroll, etc). You should notice that this doesn't work. 1. Interact with the toplevel document (highlight text, scroll, etc), and then try to interact with the subframe again. You should notice that this now works as expected. I can reproduce this on Linux and macOS, and cpeterson was able to reproduce on Windows. As far as I can tell, this only reproduces when the toplevel content has `height: 100%; overflow: auto` and the iframe has `position: fixed`.