Why is window.location.search empty?

Question

If I console.log(window.location) I get this:

Location {replace: function, assign: function, ancestorOrigins: DOMStringList, origin: "https://localhost:3000", hash: "#/account/content?hello=world"…}
ancestorOrigins: DOMStringList
assign: function () { [native code] }
hash: "#/account/content?hello=world"
host: "localhost:3000"
hostname: "localhost"
href: "https://localhost:3000/#/account/content?hello=world'"
origin: "https://localhost:3000"
pathname: "/"
port: "3000"
protocol: "https:"
reload: function reload() { [native code] }
replace: function () { [native code] }
search: ""
toString: function toString() { [native code] }
valueOf: function valueOf() { [native code] }
__proto__: Location

I expect search to be ?hello=world, but it isn't.

Why?

I'm using Chrome 35

Everything after the # (including the #) is part of window.location.hash. — gen_Eric
– gen_Eric, Commented May 21, 2014 at 17:05
Best practice is to append the named anchor at the end, see this answer: superuser.com/a/498625/12170 — neoneye
– neoneye, Commented Aug 6, 2020 at 21:27
I have the same issue with a React app. My company app has this hash in the url, some strange React format. — Matt K
– Matt K, Commented Jul 18, 2023 at 16:16

RienNeVaPlu͢s · Accepted Answer · 2014-05-21 17:03:07Z

55

Because ?hello=world isn't considered the query string in your case.
It's part of the anchor (#) which can be obtained using

window.location.hash

answered May 21, 2014 at 17:03

RienNeVaPlu͢s

7,7026 gold badges46 silver badges79 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Why is window.location.search empty?

1 Answer 1

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related