-
Notifications
You must be signed in to change notification settings - Fork 540
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Digit highjacks the click handler for some users but not others, on exact same browser config and version #420
Comments
You should set a breakpoint to figure out who is calling The problem might be related to focus jumping to the popup after it's opened, and the timing of the click (how long between mousedown and mouseup), although that doesn't really make sense either because the click event (and the popup.open() call) shouldn't happen until after mouseup. |
Hello Bill,
I will check the stack trace and try to gather additional insights.
I am not sure this is timing related though but will check that angle.
Thank you,
Sent from my BlackBerry - the most secure mobile device
From: ***@***.***
Sent: February 7, 2022 20:41
To: ***@***.***
Reply-to: ***@***.***
Cc: ***@***.***; ***@***.***
Subject: Re: [dojo/dojo] Digit highjacks the click handler for some users but not others, on exact same browser config and version (Issue #420)
You should set a breakpoint to figure out who is calling stopNativeEvents() at all. There's no way to tell from your code snippet, and I don't see it getting called at all.
The problem might be related to focus jumping to the popup after it's opened, and the timing of the click (how long between mousedown and mouseup), although that doesn't really make sense either because the click event (and the popup.open() call) shouldn't happen until after mouseup.
—
Reply to this email directly, view it on GitHub<#420 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AADEHB5IFXKZXKJU2WFKBBLU2BYC7ANCNFSM5NYYFZ4Q>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
I just realized that That whole module has probably outlived its usefulness as you can get the same effect without javascript, see https://developers.google.com/web/updates/2013/12/300ms-tap-delay-gone-away. I suggest you just disable the module. Whatever your build system is you could remap dojo/touch to an empty file, or something like that. |
In dijit.js, the function stopNativeEvents() is triggered on some browsers but not others. This is not related to a browser version or something, so this is very strange:
Triggering code:
On some user accounts, this results in a click-handler being added to the element and gobbling up events, while for other users, the click handler is never instantiated. I traced this to clickTracker being set.
Again, this behavior has been observed with users on the exact same browser setup as other users who do not experience this issue.
Thank you.
The text was updated successfully, but these errors were encountered: