Closed
Bug 792532
Opened 12 years ago
Closed 7 years ago
new about:blank context should be created for loads of javascript: URIs that can't inherit the current page's principal
Categories
(Core :: DOM: Navigation, defect)
Core
DOM: Navigation
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: Gavin, Unassigned)
References
Details
This would fix bug 728313 without regressing bug 656433. It would also make non-malicious javascript: URIs like "javascript:alert(1)" work again.
Reporter | ||
Comment 1•12 years ago
|
||
See attachment 600103 [details] [diff] [review] from bug 728313 for a failed stab in the dark that I took at this.
Comment 2•12 years ago
|
||
Hmm. So instead of running the JS in a sandbox we would nuke the existing page and run it against the new about:blank?
That might be ok, yes....
Comment 3•12 years ago
|
||
As long as we make sure web pages can't trigger it.
Reporter | ||
Comment 4•12 years ago
|
||
Yeah, exactly. I guess the nuking of the existing page could be annoying, given previous behavior, but I think it's probably better than the current behavior.
Comment 5•7 years ago
|
||
This showed up in my search results. Given bug 728313 is now fixed, I'm going to suggest wontfixing this. Changing how we load JS URIs in this way seems... a bit scary, and I don't see a good reason to do it anymore. Boris, does that sound OK?
Flags: needinfo?(bzbarsky)
Updated•7 years ago
|
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•