New issue
Advanced search Search tips

Issue 804261 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Mar 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

%22 gets unescaped when updating window.location.search

Project Member Reported by larsrc@google.com, Jan 22 2018

Issue description

Chrome Version: 63.0.3239.132
OS: Linux 4.4.0-103-generic

What steps will reproduce the problem?
(1) Navigate to a page, open dev tools
(2) Type: window.location.href = "foo%22?foo%22#foo%22";
(3) Browser will load new page. Look at the URL in the URL bar.

What is the expected result?

The URL shown is http://example.com/foo%22?foo%22#foo%22

What happens instead?

The URL shown is http://example.com/foo"?foo"#foo%22

When inspecting window.location, the values are correctly escaped. When copying the URL, the values are also correctly escaped. 

 

Comment 1 by larsrc@google.com, Jan 22 2018

Labels: OS-Mac
Also happens on Mac with the same Chrome version.
Components: Blink>Loader
Labels: -OS-Linux -OS-Mac
Status: WontFix (was: Untriaged)
I think Chrome intentionally shows un-escaped address in the omnibox bar.

You can also put escaped URL to the omnibox directly. It will results in showing unescaped URL in the omnibox, and returning escaped string on window.location.href.

Sign in to add a comment