Closed Bug 675555 Opened 13 years ago Closed 13 years ago

location.search is an empty string for about: URLs

Categories

(Core :: Networking, defect)

x86
macOS
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: int3, Unassigned)

Details

1. Go to about:home?test=1 or about:config?test=1 2. Open the Web Console and type 'window.location.search' Actual Results: window.location.search is the empty string. Expected Results: window.location.search == "?test=1"
Non-hierarchical URIs in necko don't have a query portion. In the cases above, the path is "home?test=1" and "config?test=1" respectively. In particular, these URIs match the scheme ":" opaque_part production from RFC 2396 section 3, more or less. RFC 3986 changes around the definitions so this option no longer seems to exist, but we don't implement that RFC anyway (in part because parts of it are not web-compatible). There's currently work on an updated URI RFC; once the dust settles on that we should see what things look like. But the upshot is that in your examples there is in fact no .search on that URI at the moment. The '?' character is just not special in non-hierarchical URIs.
Ah I see; thanks for the explanation!
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.