New issue
Advanced search Search tips

Issue 737911 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 737711
Owner: ----
Closed: Jun 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

Link with URL containing + is rewritten with %20 the first time it is followed, not on later clicks

Project Member Reported by whesse@google.com, Jun 29 2017

Issue description


Google Chrome	61.0.3135.4 (Official Build) dev (64-bit)
Revision	8366065c0da06984379f2d39bc85c1067d70d3dd-refs/branch-heads/3135@{#8}
OS	Linux
JavaScript	V8 6.1.191

What steps will reproduce the problem?
(1) Got to the page  https://dart-review.googlesource.com/#/c/2241/
(2) Click on the link https://chromium.googlesource.com/chromium/src/+/infra/config/cr-buildbucket.cfg in comment 3.
(3) A new page opens with the URL set to https://chromium.googlesource.com/chromium/src/%20/infra/config/cr-buildbucket.cfg#   . This page does not exist, so returns a 404
(4) Go back to the page with the link, and click a second time.
(5) A new page opens with the correct URL, https://chromium.googlesource.com/chromium/src/+/infra/config/cr-buildbucket.cfg

What is the expected result?
That the link opens with the target URL unchanged, as it does the second time you click.

This has been happening on multiple pages, all git browsing URLs with a + in them, where it is rewritten to %20 the first time the link is followed.

Opening the same page in a new tab, and repeating the steps, does not reproduce the problem.

Creating a new comment with a similar URL did not reproduce the problem.
 

Comment 1 by whesse@google.com, Jun 29 2017

This example is not reproducing with
Version 61.0.3141.7 (Official Build) dev (64-bit)
either before or after clearing all browsing data.

I will follow up if the problem reproduces again.

Comment 2 by whesse@google.com, Jun 30 2017

Mergedinto: 737711
Status: Duplicate (was: Untriaged)
This is a duplicate.  login.google.com is intercepting and rewriting somehow, not a chrome problem.

Sign in to add a comment