Closed Bug 305579 Opened 19 years ago Closed 19 years ago

XULRunner allows apps to replace toolkit chrome

Categories

(Toolkit Graveyard :: XULRunner, defect)

Product:
Toolkit Graveyard
Component:
XULRunner
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
major

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: WeirdAl, Unassigned)

Details

Suppose I have a XULRunner app with a chrome.manifest file containing:

content global content/global/

I've just succeeded in completely replacing the XULRunner
chrome://global/content with my own.  The app has broken all over the place.

This is not such a big deal for XULRunner specifically (though it's extremely
annoying), but you'd think the codebase in general would protect itself against
global and other native chrome being overridden.
The same is true for an extension when setting the following in its chrome.manifest:
content global jar:etc...

In the case of an extension the solution for the user is to use safe mode and
uninstall the extension, never install the extension again, and perhaps
blacklisting in the future. In the case of an XULRunner app wouldn't this only
be seen by the author?
We give you lots of rope, please don't hang yourself ;-)
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → WONTFIX
Product: Toolkit → Toolkit Graveyard
You need to log in before you can comment on or make changes to this bug.