Typing in the text box when commenting a merge request or issue while having a zoom value less then 100% constantly scrolls down the page when using Safari on Mac.
The workaround is to reset the zoom factor to Actual size, or zoom in.
Weirdly, zooming in seems to be a workaround. Maybe it's triggered by window size or screen resolution, such that it's an issue for me at the default zoom level but for you only when zoomed out. (I have dual 24" screens, each at an effective resolution of 2304x1296.)
I've put up with this problem for over a year now. Big part of our workflow.
I switched to Chrome due to the Safari and MR diff bug and have enjoyed getting away from the bug discussed here as well.
Unfortunately I had no luck to track it down further, as Safari gave me strange output in the debugger, e.g. by giving me brakepoints in the sentry JS code, which shouldn't be related to this issue. However, if I temporary deactivate this event listener, all seems to be fine, except the textarea doesn't grow anymore.
From my brief look today, this seems mostly fixed. It budged just a little, one time.
I'll keep an eye on it and come back if it seems stably resolved.
Typing in the text box when commenting a merge request or issue while having a zoom value less then 100% constantly scrolls down the page when using Safari on Mac.
This has been a real pain for me, but hopefully this issue provides a workaround: it works fine after reseting the zoom factor to "actual size".
I wish I could zoom out though.
Fabien Catteauchanged the descriptionCompare with previous version
Yep, this is happening with me too, only in Safari. It took me a while to realize it's a zoom issue. Although, it's causing me some trouble too, cuz' usually I zoom out on my second display, and it would be lovely to have it fixed.
Agree with others. When zoomed out by one step, the screen is moving even here when typing this message. I am using the newest Safari browser 15.3 (17612.4.9.1.8) on the newest Big Sur 12.2.1. When I reset the zoom, it's ok, but the letters are then pretty big on my 24" lcd :(.
I'm experiencing the same issue with certain zoom levels on 15.6.1 (17613.3.9.1.16). With Actual Size, there is no scrolling, but if I Zoom Out once, the page scrolls down with every letter I type.
I have a hunch this is related to the root cause of #207570 (closed). Something is measuring the scroll position, expecting an integer, but gets a float instead. That float then gets rounded explicitly or implicitly, and so the scroll position moves slightly.
This is still existing today on a brand-new, fully up-to-date Mac. I'd love to see a fix.
For further colour, it does not happen when the height of the container is constrained within the window height. As you add more text/information to the page and it extends below the bottom of the window view, then the rest of the content starts sliding down.
I was very glad to see this has already been acknowledged. Then I became very sad to see it's been 4 years without a resolution.
This did not happen on older, self-hosted GitLab instances, so it's likely a regression with something in newer versions and/or possibly specific to the cloud version.
For reference, I'm experiencing this with:
macOS Sonoma 14.1.1
Safari 17.1
85% zoom
Something I noticed is that at 85% zoom, the page scrolls a few pixels with every keystroke. However, one step down at 75% zoom, it behaves differently. At 75%, the first keystroke might scroll about 1 pixel, then subsequent keystrokes will not cause additional scrolling. At 50% the issue seems to disappear entirely.
Also worth noting: some people have noticed that Cmd+0 does not seem to help, and I was almost fooled by this. However, it's important to realize that if you have configured a default zoom level per-site (as I had) then Cmd+0 does not zoom to 100%, but rather to the site's configured default zoom - 85% in my case. I suspect this is why some people thought 100% zoom was also causing the problem.
This bug is really annoying. I suspect this 'autosize' library is also the reason why typing in a MR comment can easily take 500ms per character in Safari. Both bugs combine to make reviewing large MRs in Safari really tedious.
It'd be really good if gitlab could do one of the things @justin.mrkva suggests above please. A different option (hinted at on https://github.com/jackmoore/autosize/issues/396 would be to disable the auto-shrinking, as apparently that's the issue, though not sure there's an API for that).
Is there anyway to set a bounty on a gitlab bug? I'll happy chip in a few hundred USD...