Support clipping to the visibleRect and applying scaling from CSS transforms to OOP-iframes
Categories
(Core :: Graphics, task, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox69 | --- | fixed |
People
(Reporter: rhunt, Assigned: rhunt)
References
(Regressed 1 open bug)
Details
Attachments
(4 files, 1 obsolete file)
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Comment 1•5 years ago
|
||
Assignee | ||
Comment 2•5 years ago
|
||
visibleRect should affect both WR/layers, and scaling will only affect
layers.
Depends on D34523
Assignee | ||
Comment 3•5 years ago
|
||
This is suboptimal for when we simply change the visibleRect of an OOP-iframe,
which could happen when scrolling over a very tall iframe, but is very easy
to make sure is working correctly.
Depends on D34525
Assignee | ||
Comment 4•5 years ago
|
||
The root displayport has some assumptions built into it about being positioned at
the origin and sized to the composition bounds that seem like they only apply to
the cross process root content document. This commit changes us to avoid taking
this code path for OOP-iframes.
Depends on D34526
Assignee | ||
Comment 5•5 years ago
|
||
Even if we don't have a root displayport, the composition size is still used for
displayport margins calculations. For extremely tall iframes, this will create
a displayport that is way to big. We should instead report a composition size that
is equivalent to the visible rect for OOP-iframes.
Depends on D34527
Updated•5 years ago
|
Assignee | ||
Comment 6•5 years ago
|
||
Comment 8•5 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/e3f2d2748314
https://hg.mozilla.org/mozilla-central/rev/8e2f26c4072b
https://hg.mozilla.org/mozilla-central/rev/c024e5eced2c
https://hg.mozilla.org/mozilla-central/rev/94b369f38c53
Comment 9•5 years ago
|
||
Retroactively moving fixed bugs whose summaries mention "Fission" (or other Fission-related keywords) but are not assigned to a Fission Milestone to an appropriate Fission Milestone.
This will generate a lot of bugmail, so you can filter your bugmail for the following UUID and delete them en masse:
0ee3c76a-bc79-4eb2-8d12-05dc0b68e732
Description
•