Open Bug 1579247 Opened 5 years ago Updated 2 years ago

Make nsIFrame::IsVisibleConsideringAncestors work as expected in terms of nsDeckFrame in fission world

Categories

(Core :: Layout, defect, P5)

Product:
Core
Component:
Layout
Type:
defect

Tracking

()

Project Flags:
Fission Milestone Future

People

(Reporter: hiro, Unassigned)

References

(Blocks 1 open bug)

Details

It turns out we can't simply check PresShell::IsActive there since the function should return true even if the target document is in background tabs. (But it should return false if the target document is in a cross-process iframe in a hidden deck panel)

See Also: → 1541256
See Also: → 1578973
Summary: Make nsIFrame::IsVisibleConsideringAncestors as expected in terms of nsDeckFrame in fission world → Make nsIFrame::IsVisibleConsideringAncestors work as expected in terms of nsDeckFrame in fission world

I did push try runs this and this to tell what xul document (other than browser window and test documents) uses nsDeckFrame which has iframe as descendant element. Actually there are two documents, Scratchpad and about:addons. Scratchpad will be removed soon (bug 1519103) and about:addons is going to be de-XUL-ed soo (bug 1558982). So I am de-grading priority of this bug (I assume these bugs will be done before we ship fission).

Priority: P3 → P5

Tentatively moving all bugs whose summaries mention "Fission" (or other Fission-related keywords) but are not assigned to a Fission Milestone to the "?" triage 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

Fission Milestone: --- → ?

Fission Future or WONTFIX because we expect nsDeckFrame to be removed before we ship Fission.

block fission perf meta bug

Blocks: fission-perf
Fission Milestone: ? → Future

nsDeckFrame removal - bug 1559192.

Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.