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)

defect

Tracking

()

RESOLVED FIXED

People

(Reporter: waterson, Assigned: waterson)

References

Details

Attachments

(1 file)

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).
Attached patch proposed fixSplinter Review
Status: NEW → ASSIGNED
Target Milestone: --- → M18
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)
*** Bug 41181 has been marked as a duplicate of this bug. ***
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.

Attachment

General

Creator:
Created:
Updated:
Size: