Closed Bug 1531468 Opened 5 years ago Closed 2 years ago

Consider handling SVGObserverUtils::InvalidateRenderingObservers across oop-iframe boundaries

Categories

(Core :: Layout, enhancement, P5)

Product:
Core
Component:
Layout
Type:
enhancement

Tracking

()

Status:
RESOLVED WONTFIX
Project Flags:
Fission Milestone Future

People

(Reporter: jwatt, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [wontfix?])

Probably we shouldn't support iframes in document fragments that are observed using SVGObserverUtils but it's best to decided that here in bugzilla. If we were to support that, then we'd need a mechanism for SVGObserverUtils::InvalidateRenderingObservers calls to cross oop-iframe boundaries. For example, InvalidateRenderingObservers in nsFrame.cpp currently crosses document boundaries.

Priority: P3 → P4

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: --- → ?

Jonathan, what breaks if we don't support iframes in document fragments that are observed using SVGObserverUtils? Should answering that question or making the decision to support it block shipping Fission MVP?

Flags: needinfo?(jwatt)

Tentatively tracking for Fission Nightly (M6) until we know what this bug breaks for Fission tests or users.

Bumping priority from P4 to P3 because Mozilla's Bugzilla convention is that we no longer use P4.

Fission Milestone: ? → M6
Priority: P4 → P3
Severity: normal → N/A
Fission Milestone: M6 → Future
Priority: P3 → P5
Status: NEW → RESOLVED
Closed: 2 years ago
Flags: needinfo?(jwatt)
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.