Open Bug 1432481 Opened 7 years ago Updated 2 years ago

expose base URL on nsIGlobalObject once we have a thread-safe way to do so

Categories

(Core :: DOM: Core & HTML, enhancement, P3)

enhancement

Tracking

()

People

(Reporter: bkelly, Unassigned)

References

Details

In bug 1432272 I switched some code in dom/fetch over from using GetEntryDocument() to get a base URL over to extracting it from the nsIGlobalObject.  Currently dom/fetch has to have three separate paths for this:

* Get base URL from nsGlobalWindowInner global
* Get base URL from worker private
* Get base URL (or not) from other chrome global type

It would be nice if nsIGlobalObject* simply had a way of exposing the base URL in a uniform manner so we didn't need all these separate paths.
Priority: -- → P3
I think we're almost there. Following bug 1433958 URIs are essentially immutable (but not yet thread safe. they still have some internal mutability). I hope to have thread safety fixed in a few weeks.
Component: DOM → DOM: Core & HTML
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.