Version: 54.0.2840.71, 56.0.2908.0 checked
OS: Mac OS X 10.12.1

What steps will reproduce the problem?
(1) Enable Sticky Keys in System Preferences (Accessibility > Keyboard)
(2) Navigate to a webpage, e.g. https://en.wikipedia.org/wiki/Sticky_keys
(3) Tap command (and release), enabling it for the next interaction
(4) Click on a link

What is the expected result?
- The link opens in a new tab (command-click)

What happens instead?
- The link opens in the current tab (regular click)
- If visual feedback is enabled, the indicator still goes away, indicating that the command key was applied to the previous action, though it wasn't.


Note that while tapping command once doesn't trigger a command click, tapping command twice will result in all clicks being command-clicks until it is tapped a third time.


A brief survey of how some other contexts handle command-tap-clicks:
- Chrome *does* let you command-tap-click to highlight multiple options in a <select> element [1]
- Safari does *not* let you command-tap-click links (same as Chrome)
- iTerm2 does *not* let you command-tap-click links
- The Finder *does* let you command-tap-click to select multiple files
- The system *does* let you command-tap-click in an inactive window without raising it

[1] http://html.com/attributes/select-multiple/