Closed Bug 4269 Opened 26 years ago Closed 25 years ago

[WebShell] Relative URLs do not work in nsWebShell::LoadURL()

Categories

(Core Graveyard :: Embedding: APIs, defect, P3)

defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: mcmullen, Assigned: travis)

References

Details

Calling nsWebShell::LoadURL() with a relative URL (eg the simple name of a file in the same directory as the currently loaded URL) always fails. The reason seems to be that this code assumes all URLs are absolute, and shoves http:// in front of them. Calling this function with the absolute URL does work.
Assignee: kipp → nisheeth
Nisheeth owns the webshell...
Status: NEW → ASSIGNED
Accepting bug...
Component: Apprunner → Embedding APIs
Target Milestone: M6
Changing component to "Embedding APIs" and setting Target Milestone as M6...
John, is this bug blocking you from doing something? Please let me know if M6 is too late for this to get fixed.
I worked around it by using full resource: urls. So I am not blocked.
QA Contact: 3853 → 4130
Updating QA Contact.
Moving non-crashing layout and webshell component bugs to M8... I already have enough blockers and crashers for M6. If I fix them in time for M6, I'll move some of these bugs back to the M6 milestone. I'm keeping the M7 milestone for fixing XML bugs.
Moving this over to M10...
Target Milestone: M8 → M10
Summary: Relative URLs do not work in nsWebShell::LoadURL() → [WebShell] Relative URLs do not work in nsWebShell::LoadURL()
CCing Scott Collins, new webshell owner...
Bul re-assigning webshell bugs to the new webshell owner, Scott Collins. Scott, please adjust the target milestone assignments as you see fit. Thanks.
Target Milestone: M10 → M15
nobody seems to be blocked on this, moving to M15
(Mass-) Re-assigning [Webshell] bugs to travis, on the advice of dp, et al. Many of these may be invalid in the new world of the re-written webshell, but he certainly needs to be aware of these issues. Hope this helps you, travis.
Status: NEW → ASSIGNED
Depends on: 13374
Move to M16 for now ...
Target Milestone: M15 → M16
This is invalid now with the new design. This function is not even available anymore...
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
marking VERIFIED
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.