ontouchstart in document.documentElement
Reported by
mooseman...@gmail.com,
Mar 29 2018
|
||||||||
Issue description
Chrome Version : 67.0.3382.0
OS Version: 10.0
URLs (if applicable) :
Other browsers tested: Chrome 65.0.3325.181 OK
Add OK or FAIL after other browsers where you have tested this issue:
Firefox: OK
IE/Edge: FAIL
What steps will reproduce the problem?
1. Open DevTools console
2. Enter 'ontouchstart' in document.documentElement
What is the expected result?
boolean true
What happens instead of that?
boolean false
,
Mar 30 2018
Checked the issue on reported chrome version 67.0.3382.0 using Windows 10 and Ubuntu 14.04 with the below mentioned steps. 1. Launched Chrome 2. Opened DevTools 3. Entered 'ontouchstart' after document.documentElement But it rendered Uncaught error. Attaching the screen shot of the same. @Reporter: Could you please have a look at the screen shot and let us know if we have missed anything in the process. Any further inputs from your end may help us. Tentatively adding component Platform>DevTools, please change if this isn't apt. Thanks!
,
Mar 30 2018
https://stackoverflow.com/questions/2915833/how-to-check-browser-for-touchstart-support-using-js-jquery/2915912#answer-14320591 https://github.com/maaaaark/bcSwipe/issues/4 It is not related to Chrome DevTools issue.
,
Apr 2 2018
@Vamshi The comment from @Kozy represents the issue well. The attached screen shot shows the incorrect behavior in 67.0.3386.0 (Current canary build) on my machine. In Chrome 65.0.3325.181 (Current stable build) as well as current Firefox, this returns true. My tests with touch events appear to function correctly.
,
Apr 2 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 3 2018
See topic: https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/KV6kqDJpYiE Do you have a specific project that is causing you issues that you cannot work around?
,
Apr 4 2018
Able to reproduce the issue on reported chrome version 67.0.3382.0 and on the latest chrome version 67.0.3387.0 using Windows-10, Mac 10.12.6 and Ubuntu 14.04. As the issue is seen from M60(60.0.3112.0) considering it as non-regression and marking it as Untriaged. Thanks!
,
Apr 5 2018
,
Jun 21 2018
Closing this since there is no feedback provided after 2 month. mooseman...@ please see comment 6 for detail. If you have any a specific project that cannot work around, please feel free to comment if you have additional feedback |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by viswa.karala@chromium.org
, Mar 29 2018