Reduce bad usage of contentWindowAsCPOW and contentDocumentAsCPOW

NEW
Unassigned

Status

()

Firefox
General
3 years ago
11 months ago

People

(Reporter: mconley, Unassigned)

Tracking

(Blocks: 1 bug, {meta})

unspecified
x86
All
Points:
---

Firefox Tracking Flags

(e10s-)

Details

There are portions of the codebase that use the contentWindowAsCPOW and contentDocumentAsCPOW properties on a <xul:browser> (remote or not)[1]. 

We should examine each point we use one of these properties, and see what happens to the CPOW - tracing whether or not we store them, and figuring out how much traffic goes across them during their lifetime. If we can identify some bad offenders, we should then find a way of not using CPOWs for those cases.

[1]: These properties are explicitly CPOWs in the remote browser case
tracking-e10s: --- → ?
tracking-e10s: ? → +
Whiteboard: meta
Keywords: meta
Whiteboard: meta
tracking-e10s: + → ?
tracking-e10s: ? → m8+

Updated

2 years ago
tracking-e10s: m8+ → -
You need to log in before you can comment on or make changes to this bug.