I can not reproduce this issue. It looks like there is an extension which changes the behavior of the double click. Can you disable all the extensions and try again?

I disabled all the extensions but I can still see the issue. I could even reproduce it on Firefox and Chrome across several Windows versions using browserling.

Here's a gif that shows the bug: https://imgur.com/a/76BN8iG

Thank you for providing the information. Since you observed the same behavior across different browsers, I guess that the scroll event (or other events that causes the page to scroll up) is emitted by your system. Maybe the mouse is broken, maybe there is an application capturing the double click events and emitting other events.

Can you try two more things to confirm the root cause of the issue?

1. Try to double click pages from other websites, will the pages scroll up?
2. Try to double click https://go.dev/doc/tutorial/workspaces on another computer, will the page scroll up?

If you know how to use Spy++, you can use it to check what messages are emitted. It's shipped with Visual Studio. If you don't want to install Visual Studio, you can download it from https://github.com/westoncampbell/SpyPlusPlus. Here is my message options:

And here is the messages captured on my computer:

Looks like this doesn't happen if you use a mouse. It only happens if you use laptop touchpads (I verified this on 2 separate laptops, both on Windows), and to a certain extent, touch devices. I could reproduce this issue on an iPhone 13 as well, on both Chrome and Safari.

OK, I have managed to reproduce the described behavior.

• touchpad on desktop: click->tap->move up
• mobile phone: long tap->move up.

If this is your case, then I think the behavior is expected and there is nothing wrong.

I'm not sure how this is expected behavior. Double tap on a touchpad should select the text, not scroll it up automatically.

The Go docs website is the only website where this happens. All other websites select text when double tapped with a touchpad.

If you move your finger unintentionally on the second tap, the double tap will be recognized as click->tap->move by the system. Can you confirm whether this is your case first?

Nope. The issue happens without moving your finger at all, with a simple double tap on a word.

Can you use Spy++ to capture the messages as suggested in #52917 (comment)?

I could use it if you really wanted me to, but I don't think this is a problem of my system or my mouse emitting random events. I discussed this with my friend (who could reproduce this issue too, btw, on a completely different computer) and it seems this is a widespread chrome issue, actually. It affects all websites, just to a far lesser extent than it affects the golang documentation website. Also, even with using a touchpad, it should be a "double-tap", not a "double-press", if that makes sense.

To reproduce it on other websites, if you double tap to select a word and the word is almost (but not completely) out of the screen, Chrome will scroll up in the same weird manner. For example, double tapping any of these "half" words will reproduce this issue on Wikipedia.

Now, I don't know why it affects the Go website more than the other websites. Double tapping any of these words will reproduce the issue:

It probably has to do something with the line-height of the body, I think. I increased the line-height on body to 10 and I could reproduce the issue when the words were far below the screen too.

Since this issue is not specific to the golang documentation website, and it's more like a browser, system or hardware issue, maybe we should avoid discussing it here so that we won't make too many noises.

I still incline to the guess that the behavior is a "select and drag outside of the viewport". If you still want to diagnose this issue, please find me on slack. And if we find something, we can report back here.

Thank you!

How do I find you on slack?

@a3y3 is right, I can reproduce this as well. @ZekeLu please make sure to position the text exactly as on the GIF. The problem is in _content/css/styles.css on line 250 scroll-padding-top: 4.6875rem. Disabling this rule solves the issue

I can create a CL for this, but I asked the original author of this line about his intent. It was almost 2 years ago, probably he won’t recall the reason behind the line, but let’s wait and see

@looshch Excellent!

I don't have a touchpad right now. But when I set scroll-padding-top to a big value (for example, 100rem), select the text near the top of the veiwport, and move my mouse at a very little distance, it scrolls to the top of the page very fast. When I set it to 0 and do the same thing, it just scrolls up a little. So obviously, scroll-padding-top: 4.6875rem will cause trouble on touchpad more easily (I can not reproduce it on touchpad before because I have the habit to touch the touchpad carefully 😃 ).

The value is set in this commit: golang/website@5571d04. But there is not information about why it's set. I think it's safe to remove it.

Update
When scroll-padding-top is set to 100rem, selecting the text near the top of the veiwport with a mouse will make the page scroll up. But double click the mouse to select text won't make it scroll up.

Change https://go.dev/cl/409014 mentions this issue: _content/css: fix content auto-scrolling on selection

I’m glad it could be reproduced! As you can imagine, it can get annoying because some people like to read by double tapping on text and selecting it as they read along - and that’s not possible because of the scrolling issue.

I do wonder why the content scrolls up only on touchpad and not a mouse, though.

This was probably added with the sticky header to make anchor links snap their scroll position below the header content. We removed the sticky header at some point so this scroll fix is no longer necessary. Thanks for the investigation and fix!