1144149 - [meta] gBrowser's contentDocument and contentWindow properties are not available for remote tabs

Status: RESOLVED FIXED

(Firefox :: Tabbed Browser, defect, P5)

Description

[Mike Conley (:mconley) (:⚙️)]

A quick DXR shows gBrowser.contentDocument being used in a number of places. The contentDocument property maps to this.mCurrentBrowser.contentDocument, which is undefined in the e10s case.

Same goes for contentWindow.

We should probably add gBrowser.contentDocumentAsCPOW/contentWindowAsCPOW and change all in-tree usage of gBrowser.contentDocument/contentWindow to use gBrowser.contentDocumentAsCPOW/contentWindowAsCPOW instead (much like we did in bug 1051017).

We should then probably mark gBrowser.contentDocument/contentWindow as deprecated.

Comment 1

[Mike Conley (:mconley) (:⚙️)]

I need to file bugs for the places that browser code uses these accessors.

Comment 2

[Mike Conley (:mconley) (:⚙️)]

Ok, I've filed all of the usages of gBrowser.contentWindow and gBrowser.contentDocument I could find.

All of the test instances will take advantage of shims and should be OK - I've marked those as tracking-e10s:later. For the non-test instances, I've nommed them for triage.

I figure we can use this bug to introduce the gBrowser.contentWindowAsCPOW and gBrowser.contentDocumentAsCPOW shortcuts.

Comment 3

[Andrew McCreight [:mccr8]]

CPOWs have been removed.