Tidy a bit the relationship between nsPresContext and nsDocShell.

RESOLVED FIXED in Firefox 67

Status

()

enhancement
RESOLVED FIXED
5 months ago
5 months ago

People

(Reporter: emilio, Assigned: emilio)

Tracking

(Blocks 1 bug)

unspecified
mozilla67
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(firefox67 fixed)

Details

Attachments

(1 attachment)

Make it always forward to the document's docshell. We rely on it being setup by the time our stuff runs, and we cannot have multiple pres contexts per document in different docshells anymore.

This allows me to also move some state to the document (about whether it's currently loaded in a chrome docshell (nsPresContext::mIsChrome) and whether it's a chrome origin image (nsPresContext::mIsChromeOriginImage), which will help for bug 1490401 / bug 1418159.

Make it always forward to the document's docshell. We rely on it being setup by
the time our stuff runs, and we cannot have multiple pres contexts per document
in different docshells anymore.

This allows me to also move some state to the document (about whether it's
currently loaded in a chrome docshell (nsPresContext::mIsChrome) and whether
it's a chrome origin image (nsPresContext::mIsChromeOriginImage), which will
help for bug 1490401 / bug 1418159.

The pres context already relies on having the docshell available and we don't
handle dynamic changes to it.

Pushed by ealvarez@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/8ed0dbecf030
Tidy the relationship between the doc shell and the pres context. r=qdot
Status: NEW → RESOLVED
Closed: 5 months ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla67
You need to log in before you can comment on or make changes to this bug.