New issue
Advanced search Search tips

Issue 651419 link

Starred by 4 users

Issue metadata

Status: Fixed
Owner:
Closed: Dec 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

When alt + clicking on a link and there is also a mouseup handler that selects some text, the click event doesn't fire.

Reported by sjom...@gmail.com, Sep 29 2016

Issue description

Chrome Version       : 53.0.2785.116 m
Operating system     : Windows 10 pro 64 bit

URLs (if applicable) : https://jsfiddle.net/SamMiller/c7tgx5Lw/
Other browsers tested:
  Add OK or FAIL, along with the version, after other browsers where you
have tested this issue:
    Firefox: OK (49.0.1)
      IE 11: OK (11.494.10586.0)
       Edge: OK (25.10586.0.0)
     Safari: OK (9.1.1 (9537.86.6.17)

When alt + clicking on a link and there is also a mouseup handler that selects some text, the click event doesn't fire. Selecting the text doesn't have to be on the mouseup handler, it can also happen if its in a focusin handler for instance. I believe it is because alt + click in Chrome attempts to download the link target which could be getting confused when some text is selected.

What steps will reproduce the problem?
(1) Navigate to https://jsfiddle.net/SamMiller/c7tgx5Lw/
(2) Open the console.
(3) Click on the red square so that it has focus.
(4) Alt + click on the link.
(5) Notice that the console never reports that a click happens.
(6) Now just click on the link without holding the alt key down.
(7) Notice that the console reports the clicks on each of the elements.

What is the expected result?

The click event should fire even if alt is being held down.

What happens instead?

The click event never fires.

Please provide any additional information below. Attach a screenshot if
possible.

 

Comment 1 by sjom...@gmail.com, Sep 29 2016

This bug is also present in the canary build 55.0.2875.0 canary (64-bit)
Cc: dtapu...@chromium.org mustaq@chromium.org
Components: Blink>Input
Labels: Hotlist-Input-Dev
Owner: nzolghadr@chromium.org
Status: Assigned (was: Unconfirmed)
Confirmed that this behaviour is different between Linux and Windows on Chrome.
Status: Fixed (was: Assigned)
This is fixed on the latest Chrome on Windows and behaves the same on Linux as well. Feel free to open a new bug if you see another similar bug.

Sign in to add a comment