Chrome anchors are broken, Google has locked and is ignoring bug thread

#1

Post by arghblarg » Thu, Sep 03, 2020, 7:44 PM UTC

Chrome anchors are broken, Google has locked and is ignoring bug thread
support.google.com

Re: Chrome anchors are broken, Google has locked and is ignoring bug thread

#2

Post by cmwelsh » Thu, Sep 03, 2020, 8:28 PM UTC

I noticed this at work when creating anchor links within our wiki - I thought perhaps I was doing something wrong. Can you elaborate on the submission title?

Re: Chrome anchors are broken, Google has locked and is ignoring bug thread

#3

Post by javajosh » Thu, Sep 03, 2020, 8:30 PM UTC

That's odd, I use Chrome and haven't seen anything amiss. Can someone provide a Codepen or something that demonstrates the issue?

Re: Chrome anchors are broken, Google has locked and is ignoring bug thread

#4

Post by monkpit » Thu, Sep 03, 2020, 8:31 PM UTC

That workaround though...

Re: Chrome anchors are broken, Google has locked and is ignoring bug thread

#5

Post by adrianmonk » Thu, Sep 03, 2020, 8:32 PM UTC

Isn't this from 8-12 months ago?

That thread looks like it was created on 8/14/19 and the last comment was made 1/14/20.

I think I did notice some issue with anchors, but if so, this doesn't seem like the right support thread.

EDIT: Also the title mentions Chrome 76, and I'm on Chrome 85.

Re: Chrome anchors are broken, Google has locked and is ignoring bug thread

#6

Post by rohansingh » Thu, Sep 03, 2020, 8:38 PM UTC

Nothing to see here:

  Thought it was a bug but it's just a feature difference between browsers.
  
  The first time the page loads with an anchor in the url: `http://somesite.com/#gohere` it should load and go to that location on the page.
  
  But if you scroll to the bottom for example, then reload the page or put the cursor in the URL bar and press "Return/Enter"... the page will simply reload exactly where you are.

Re: Chrome anchors are broken, Google has locked and is ignoring bug thread

#7

Post by jackinloadup » Thu, Sep 03, 2020, 8:41 PM UTC

This tells me either they don't have to pass their automated testing suite to do releases, or worst of all the functionality is broken on purpose. Anchors are HTML 101. Something is really messed up somewhere for this to be an issue for 8 production releases now. This started in Chrome 76 and 84 is the current version.

Re: Chrome anchors are broken, Google has locked and is ignoring bug thread

#8

Post by falcolas » Thu, Sep 03, 2020, 8:45 PM UTC

rohansingh wrote: post #6

Nothing to see here: Thought it was a bug but it's just a feature difference between browsers. The first time the page loads with an anchor in the url: `http://somesite.com/#gohere` it should load and go to that location on the page. But if you scroll to the bottom for example, then reload the page or put the cursor in the URL bar and press "Return/Enter"... the page will simply reload exactly where you are.

It's not a "feature difference". It's a change since it worked in a prior version of Chrome.

Re: Chrome anchors are broken, Google has locked and is ignoring bug thread

#9

Post by falcolas » Thu, Sep 03, 2020, 8:46 PM UTC

monkpit wrote: post #4

That workaround though...

It's missing a /s. At least, I hope they just forgot to add that.

Re: Chrome anchors are broken, Google has locked and is ignoring bug thread

#10

Post by barbegal » Thu, Sep 03, 2020, 8:48 PM UTC

rohansingh wrote: post #6

Nothing to see here: Thought it was a bug but it's just a feature difference between browsers. The first time the page loads with an anchor in the url: `http://somesite.com/#gohere` it should load and go to that location on the page. But if you scroll to the bottom for example, then reload the page or put the cursor in the URL bar and press "Return/Enter"... the page will simply reload exactly where you are.

Yeah there are two competing needs here. Users expect to stay in the same location on the page if they refresh it or if they go to another page and use the back button. Users also expect that when the URL contains an anchor then they go to the location of that anchor. It's a tough issue to find the balance between these two user needs but I think the behaviour implemented by Chrome is good. These days it is very rare that a user refreshes a page, and when they do most users expect to stay in the same location on the page.