Middle click not fired ?
Reported by
ad...@murielfrenchcouture.fr,
Dec 21 2016
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2955.0 Safari/537.36 Steps to reproduce the problem: Chromium Win_x64 branch. I’m a dressmaker, I’m not sure that a bug... Sorry for inconvenance. 1. Go on : http://codepen.io/anon/pen/GNeymQ or https://jsbin.com/xakorucufi/edit?html,js,console,output 2. Middle click the "skxdcfvgbhnj" button 3. The alert popup not fire. In a fresh update windows 8.1 virtual machine I download a fresh Chromium Win_x64 version from storage.googleapis.com/chromium-browser-snapshots/index.html At every version, I of course reset the fresh update windows 8.1 virtual machine. So it always the same working context. Here the result : 56.0.2910.0 (64bits) 430008 = FIRE NOT the middle click 55.0.2867.0 (64bits) 419794 = FIRE NOT the middle click 55.0.2854.0 (64bits) 417241 = FIRE NOT the middle click 55.0.2854.0 (64bits) 416922 = OK : Fire the middle click… 55.0.2852.0 (64bits) 416603 = OK : Fire the middle click… 55.0.2847.0 (64bits) 415964 = OK : Fire the middle click… 55.0.2841.0 (64bits) 414687 = OK : Fire the middle click… 54.0.2818.0 (64bits) 409579 = OK : Fire the middle click… 52.0.2716.0 (64bits) 389148 = OK : Fire the middle click… Because every step take me 25 minutes, I can cut between 416922 and 417241 but the change occur between this two versions : 55.0.2854.0 (64bits) 416922 (OK) < ??? < 55.0.2854.0 (64bits) 417241 (NOK) If it’s a normal security or sandbox evolution or worse a mistake from me, I apologize for opening this issue and take time to the developer. Just close it. Thank you in any case for your attention on this request. Regards. What is the expected behavior? Javascript popup "Middle click" when you middle click the button. What went wrong? It fire the left click/popup on every versions, no problem here. But the middle click/popup fire in version 55.0.2854.0 (64bits) 416922 BUT NOT in version 55.0.2854.0 (64bits) 417241 The change occur between this two versions. Did this work before? Yes See description… Chrome version: 57.0.2955.0 Channel: dev OS Version: 6.3 Flash Version: 24.0.0.186
,
Dec 21 2016
Erratum : read 416924 instead of 416922… (Result of bisection method between 416603 and 417241)
,
Dec 21 2016
I suppose "Needs-Bisect" is a bisection ? Here the result : The middle click fire in => snapshots/Win_x64/417067/ (See attachement) But not in => snapshots/Win_x64/417040/ (no popup) So the change occur between (417040) and (417067). Thanks.
,
Dec 21 2016
Able to reproduce this issue on windows 7, Mac 10.12.2 ,Linux Ubuntu 14.04 with Chrome stable version-55.0.2883.87 & Latest Canary-57.0.2957.0. Manual Bisect: ------------- Bad Build—55.0.2855.0--Revision--417475 Good Build—55.0.2853.0--Revision--416812 Provided below info as per revision bisect: ------------------------------------------- You are probably looking for a change made after 417052 (known good), but no later than 417053 (first known bad). CHANGELOG URL: ----------------- The script might not always return single CL as suspectas some perf builds might get missing due to failure. https://chromium.googlesource.com/chromium/src/+log/3eda8caca348d8c2c2f72d28af48e0757f83d1f2..7be81ca9b22fe6abb5a96d200f77167cae987b5f Possible suspect: ------------------ https://chromium.googlesource.com/chromium/src/+/7be81ca9b22fe6abb5a96d200f77167cae987b5f Review-Url: ----------- https://codereview.chromium.org/2302513002 nzolghadr@ Kindly take a look and please help us to reassign this issue to a right owner if not with respect to this change. Thanks.!
,
Dec 21 2016
Found the « problem » : It’s a new behavior from Chromium 55… [...] This behavior changed in Chrome 55. From now on we send click event for primary button of the input device only. In the case of mouse it will be left button. For non-primary buttons we send a new event called "auxclick" [...] Related : https://bugs.chromium.org/p/chromium/issues/detail?id=670739 Related : https://bugs.chromium.org/p/chromium/issues/detail?id=671387 I will update my code / extension according to this change behavior. Sorry for inconvenance about not seeing this behavior change ! I wish you all very happy feasts.
,
Dec 21 2016
Thanks for updating your extension to use this new event. Let us know if there is anything else.
,
Dec 21 2016
|
||||
►
Sign in to add a comment |
||||
Comment 1 by ajha@chromium.org
, Dec 21 2016