Clicking on extension icon when popup is already visible, randomly fails to hide it
Reported by
teo8...@gmail.com,
Jan 21 2017
|
|||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36 Steps to reproduce the problem: 1. click on an extension's icon, so the extension's popup shows up 2. click on the icon again What is the expected behavior? Every click should systematically toggle the popup. So if the popup is not currently visible it should show up, if it is visible it should hide. What went wrong? When the popup is already visible, clicking on the icon will sometimes hide it as expected, while sometimes it will cause the popup to flash, i.e. hide and show up immediately again. It looks utterly random at first, but I'm under the impression the behavior depends on the duration of the click. If the click is very, very fast (i.e. very little time elapses between pressing and releasing the mouse button), it works as expected; if the click is not fast enough (the threshold being way below the reasonable duration of a typical click), then it will exhibit the unexpected behavior, making the popup flash instead of hiding it. Obviously this doen't make any sense. Did this work before? N/A Chrome version: 55.0.2883.87 Channel: stable OS Version: Flash Version: Shockwave Flash 24.0 r0
,
Jan 23 2017
Unable to reproduce this issue on Ubuntu 14.04 using chrome latest stable M55-55.0.2883.87 by following steps mentioned in the original comment. Teo@ - Could you please confirm that is this issue is consistently reproducible for the all the extensions or specific to any particular one? If yes, could you please name them. Thanks!
,
Jan 23 2017
I have the same version of chrome 55.0.2883.87 on Ubuntu 16.04
Yes it happens with all extensions.
Have you tried varying the "length" of your clicks, i.e. the time span between pressing and releasing the button? For me, the issue systematically happens if the click is longer (the popup is closed on press and reopened on release), while the behavior is almost as expected (closed on press and not reopened; should actually be closed on release) if the click is super-fast, the threshold being much lower than a reasonable one for a click (regardless of the fact there's no reason why there should be any threshold whatsoever).
Note that comment 1 does not describe the issue accurately: it has nothing to do with the time since the previous click, it only has to do with the time between the press and the release.
I don't know why you close the popup on press rather than on release (especially given you do open it on release). I do understand the reasoning about treating a double-click as a single click ("non-geeks tend to double-click on everything") but I can't see (A) that being a reason for hiding the popup on press rather than on release nor (B) how in any way that leads to this issue. If anything, I'd expect that avoiding a double click to be treated as two separate clicks would have the side effect of missing a too-quick second click, but the issue here is completely different.
,
Jan 24 2017
,
Jan 31 2017
Thank you for providing more feedback. Adding requester "brajkumar@chromium.org" for another review and adding "Needs-Review" label for tracking. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 13 2017
Cleaning up "Needs-Review" label as we are not using this label for triage. Ref bug 684919
,
Mar 13 2017
,
May 12 2017
As per comment #1 looping @rdevlin.cronin for more updates on this issue.
,
May 12 2017
> As per comment #1 Note my comment 3. Comment 1 talks about double clicks. This isse has nothing to do with double clicks.
,
Aug 16 2017
I can reproduce this bug in GTK+ based desktops, but not in QT based: 1. Click the upper right side of Chromium, click on an extension icon. 2. Click on it again for hiding it. Result: the extension menu hides for a while, but after a fraction of a second it's shown again. Like if there was an additional click.
,
Aug 16
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Aug 16
Fixed for me.
,
Aug 16
It's not fixed, I'm still observing it. Please reopen. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by woxxom@gmail.com
, Jan 21 2017