mousedown event not firing on touchscreen capable desktops on Chrome Browser

419 views
Skip to first unread message

gerbil...@gmail.com

unread,
Oct 21, 2013, 7:49:08 AM10/21/13
to lim...@googlegroups.com
Hi,

I'm having issues getting the mousedown event to fire when a button is clicked with a mouse in Chrome on a touchscreen capable desktop.

Simple button setup..

goog.events.listen(goButton, [ 'mousedown'], function (e) {
})

This works on all major browsers and on both windows and OSX with no problems.

However on touchscreen capable desktops such as the HP TouchSmart 600, and Package Bell OneTwo L5861, this event just will not fire at all in Chrome..

I've tried adding touchstart, enabling/disabling touchscreen ability, enabling experimental touch events in chrome://flags/ with no joy whatsoever.

The event will fire correctly (with touchstart) when using a touchscreen of course, just not when using a mouse.

Has anyone else come across this? 

Cheers

Tõnis Tiigi

unread,
Oct 22, 2013, 4:45:47 AM10/22/13
to lim...@googlegroups.com, gerbil...@gmail.com
I did not see this use case when writing this code. All mouse events are disabled when you are in a touch device because the touch devices also try to simulate mouse events and that can result double dispatches.

The early return is in here https://github.com/digitalfruit/limejs/blob/3afb1f3f79123f8110e565a457092839db51fba2/lime/src/node.js#L1005 and also in the unlisten() function. Try you code without this return or maybe try to detect the HP Touchsmart there. If you find a general solution then send a pull request.

gerbil...@gmail.com

unread,
Oct 22, 2013, 5:48:07 AM10/22/13
to lim...@googlegroups.com, gerbil...@gmail.com
PERFECT!

Tested on the Packard Bell OneTwo and (after commenting out the early return) it works, will update our live code and ask the other users to test later. Will look for a general solution once we've a bit more time.

Thankyou for that fast response, much appreciated.

johnson....@gmail.com

unread,
Apr 19, 2015, 5:24:47 PM4/19/15
to lim...@googlegroups.com, gerbil...@gmail.com
Was this or another fix ever implemented back into a LimeJS build? I'm running into the same issue.
Reply all
Reply to author
Forward
0 new messages