New issue
Advanced search Search tips

Issue 646008 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 646738
Owner:
Closed: Sep 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug



Sign in to add a comment

The hash (#) in URLs does not let the page scroll to the correct position

Reported by h...@xanland.nl, Sep 12 2016

Issue description

Chrome Version       : 55.0.2853.0 dev-m (64-bit)
OS Version: 10.0
URLs (if applicable) : -
Other browsers tested:
  Add OK or FAIL after other browsers where you have tested this issue:
     Safari 5: OK
  Firefox 4.x: OK
     IE 7/8/9: OK

What steps will reproduce the problem?
1. Go to https://sa-mp.nl/about/frequently-asked-questions.html
2. Click on "How does Las Venturas Playground's banking system work?"
3. URL changes to: https://sa-mp.nl/about/frequently-asked-questions.html#q-finance-banking
3. ...
4. NO WIN

What is the expected result?
That the page should scroll to the correct anchor name equal to the part after the hashtag.

What happens instead of that?
Nothing. Although the URL changes as described in step 3, the page is not scrolled towards the correct anchor name.

Notes?
Immediately go to the specified URL does not result in the expected result either.

UserAgentString: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2853.0 Safari/537.36
 

Comment 1 by peter@chromium.org, Sep 12 2016

Cc: sunyunjia@chromium.org bokan@chromium.org
Components: Blink>Scroll
Labels: -Pri-3 OS-Linux OS-Mac Pri-2
Status: Untriaged (was: Unconfirmed)
Summary: The hash (#) in URLs does not let the page scroll to the correct position (was: The hashtag (#) in URLs does not let the page scroll to the correct position)
I can reproduce this. The bisect range is as follows:

https://chromium.googlesource.com/chromium/src/+log/a8d8427d83905a9fc64242dde7b21f1a8eda839c..6380c181f2dd0111c810da675ecce705701de822

+bokan and sunyunjia, since both of you made scroll-related commits in the range. Any idea?

Comment 2 by bokan@chromium.org, Sep 12 2016

Cc: -sunyunjia@chromium.org
Owner: sunyunjia@chromium.org
Status: Assigned (was: Untriaged)
Unlikely to be caused by my patch. Could you please take a look see if this is a regression caused by your patch?

Comment 3 by bokan@chromium.org, Sep 12 2016

Labels: Hotlist-Input-Dev
Sure let me take a look at it.
Status: Started (was: Assigned)
Mergedinto: 646738
Status: Duplicate (was: Started)

Sign in to add a comment