652736 - The add-ons manager (and probably other privileged UI) should be loaded in a chrome docshell rather than a content docshell

Status: NEW

(Firefox :: Tabbed Browser, defect)

Description

[Dave Townsend [:mossop]]

Apparently loading chrome UI in a content docshell is a big problem that needs to be fixed

Comment 1

[Dave Townsend [:mossop]]

Wonder if this is easier done from the docshell stuff by having a new type for the browser element where if the page loaded is non-privileged then it gets a content docshell and if it is privileged then it gets a chrome docshell.

Comment 2

[Tony Mechelynck [:tonymec]]

This bug is billed as a "Firefox" bug but once (if ever) bug 286651 gets FIXED (in Core::Security), SeaMonkey and Thunderbird will be in the same position. Can this be fixed once, somewhere in Core or in Toolkit, or will it have to be fixed three times, once for each of the three applications (which of course would mean two additional dependencies blocking bug 286651)?

Comment 3

[Dave Townsend [:mossop]]

(In reply to comment #2)
> This bug is billed as a "Firefox" bug but once (if ever) bug 286651 gets FIXED
> (in Core::Security), SeaMonkey and Thunderbird will be in the same position.
> Can this be fixed once, somewhere in Core or in Toolkit, or will it have to be
> fixed three times, once for each of the three applications (which of course
> would mean two additional dependencies blocking bug 286651)?

Really depends how it is fixed, my suspicion is that it will require changes to the tabbrowser implementation, hence why I filed it here, which would mean it'd need to be fixed everywhere.

To my knowledge bug 286651 isn't on the cards to actually be fixed, but we'd like to avoid that situation where possible.