Sluggish text input on github.com
Reported by
m...@muanchiou.com,
May 30 2018
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.181 Safari/537.36 Steps to reproduce the problem: 1. As a repository collaborator, navigate to https://github.com/muan/194-labels/issues/new 2. Type in the issue title field 3. Observe sluggish input 4. As a repository collaborator, navigate to https://github.com/muan/195-labels/issues/new 5. Type in the issue title field 6. Observe normal input (I am happy to add anyone to these two repositories to reproduce this, just give me a github handle.) What is the expected behavior? Expect input performance to be normal or at least not be affected by number of labels in a repository or hidden markup on a page. What went wrong? Input is sluggish. Did this work before? N/A Chrome version: 66.0.3359.181 Channel: n/a OS Version: OS X 10.13.4 Flash Version: Shockwave Flash 29.0 r0 The sluggish input problem goes away if the repository has 195+ labels, but remains sluggish around 100~194 labels. It is also possible to reproduce this bug by simply adding/removing labels in the same repository. It requires a repository collaborator to reproduce this issue, because only then the label menu is rendered. The issue persists with JavaScript disabled and stylesheets removed. For convenience here's a link to the same video attached: https://cl.ly/3i1j3624300q
,
May 30 2018
Would you mind trying in Chrome Canary, too, to see if the issue's already been fixed?
,
May 31 2018
,
May 31 2018
> Would you mind trying in Chrome Canary, too, to see if the issue's already been fixed? Ah, thanks. I should've checked that first. And yes it seems fixed in Canary. I then also upgraded to the latest 67.0.3396.62, which also does not have this problem. ⭐ Would you be able to point me to a place where I might be able to find more information about the cause of this? I'm just very curious about what might have been the issue. Thanks!
,
May 31 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
May 31 2018
It's difficult to say! To pin down a fix, I'd usually fetch some more information about the known broken/fixed versions from https://omahaproxy.appspot.com/, and then do one or more of these three things: 1. Search the bug tracker for bugs closed in the right time period: https://bugs.chromium.org/p/chromium/issues/list?q=typing+slow+closed%3E2018-3-1 2. Look at the list of commits between the two versions and use cmd+F to look for keywords: https://chromium.googlesource.com/chromium/src/+log/66.0.3359.181..67.0.3396.62?n=200000 3. Use bisect-builds.py to try on different versions of Chrome in the range: https://www.chromium.org/developers/bisect-builds-py I'd be happy to give #3 a quick try myself because I may have access to a more granular set of builds, if you want to add me to those repos (@s4y). If that doesn't find it, I'll leave it up to you :-).
,
May 31 2018
I'll mark this WontFix for now, but if we find the culprit I can make it a dupe, instead.
,
May 31 2018
Thank you! I've added @s4y to the repos. I'll give #2 a go too.
,
Aug 6
I just had a chance to try this out and, unfortunately, I couldn't trigger the original problem. Do you know if anything happened to mitigate it, or if I did something wrong (see attached*)? Otherwise, this may have to remain a mystery! --- * There's one hiccup visible in the video, but I think that may have been me letting go of the key. Typing was smooth — I tried it several times. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by m...@muanchiou.com
, May 30 2018