Closed
Bug 41182
Opened 24 years ago
Closed 24 years ago
first-time chrome: load of XUL file gives document "res:" URL
Categories
(Core :: XUL, defect, P3)
Core
XUL
Tracking
()
RESOLVED
FIXED
M18
People
(Reporter: waterson, Assigned: waterson)
References
Details
Attachments
(1 file)
940 bytes,
patch
|
Details | Diff | Splinter Review |
The first time you load a XUL document (or, every time you load it, if you've turned off your XUL cache), the document will get a base URL that is a "resource:" URL rather than a "chrome:" URL. This caused some of Mitch's security checking code to go awry when it expected to find something with a "chrome:" URL. He's since fixed it, but I'm concerned there may be other problems waiting to happen. I'm attaching a patch that sets the "originalURI" attribute on the resource channel after creating it. Let me know if it looks sane (esp. warren & mscott).
Assignee | ||
Comment 1•24 years ago
|
||
Assignee | ||
Updated•24 years ago
|
Status: NEW → ASSIGNED
Target Milestone: --- → M18
Comment 2•24 years ago
|
||
Looks good, although checking that the result is non-null is bullshit. That should be handled by the NS_FAILED on the line above. If anything, assert that it's non-null, or better yet, let it crash on the -> operator so that the caller will fix their broken code that doesn't return a proper error value. (pet peeve)
Assignee | ||
Comment 4•24 years ago
|
||
fix checked in, r=warren. i took out the offensive part.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•