Open Bug 1708243 Opened 2 months ago Updated 4 days ago

Stop depending on framescripts with `ExtensionGlobal`

Categories

(WebExtensions :: General, defect, P2)

defect

Tracking

(Fission Milestone:M8)

ASSIGNED
Fission Milestone M8

People

(Reporter: nika, Assigned: zombie, NeedInfo)

References

(Blocks 3 open bugs)

Details

Currently, whenever a messagemanager for a tab is created, a tab-content-frameloader-created notification is fired from a framescript loaded by an extension. As we don't load framescripts for out-of-process subframes, this means that the observer notification to create ExtensionGlobal objects (https://searchfox.org/mozilla-central/rev/3aef835f6cb12e607154d56d68726767172571e4/toolkit/components/extensions/ExtensionProcessScript.jsm#146-150) will never fire, and any functionality tied to these objects will be broken in extension code for out-of-process iframes.

It appears this functionality is largely used to implement getFrameData which is used to fetch information about tabId, windowId, devtoolsToolboxInfo, and viewType for a particular frame. These getters will likely behave incorrectly in cross-origin subframes.

Blocks: 1708245

Fission M8

Severity: -- → S3
Fission Milestone: ? → M8
Priority: -- → P2

Assigning to zombie as he's looking into this.

Assignee: nobody → tomica
Status: NEW → ASSIGNED

Tom, what's the latest status for this?

Flags: needinfo?(tomica)
You need to log in before you can comment on or make changes to this bug.