Peter-Paul Koch
@patrick_h_lauke @Paul_Kinlan Redid tests with touched: Chrome has gone down to 200ms. BUT width=dw still doesn't cancel delay on Nexus.
-
@Paul_Kinlan Well, I can assure you it doesn't work on the Nexus 7.
Paul Kinlan
-
-
@Paul_Kinlan@ppk Does it repro on subsequent taps? I haven't been able to reproduce any consistent issue like that on Chrome 34.0.1847.114 - View other replies
-
@RickByers@Paul_Kinlan Exactly the same Chrome version, as well. Maybe switch to an old Nexus 7? Or a new one? -
@ppk@Paul_Kinlan Thanks, very weird. I only have 2013 Nexus 7 here, but will get a 2012 one to test tomorrow. -
@RickByers What are you seeing? 200-250ms or 1-10? /cc@Paul_Kinlan -
@ppk ~250ms on first tap, ~10ms thereafter (we have a fix for that which will be in Chrome 36 (http://crbug.com/360602 ) /cc@Paul_Kinlan -
@RickByers I never saw that one, and it wasn't reported to me, either. Odd. /cc@Paul_Kinlan -
@ppk@Paul_Kinlan We confirmed old (2012) Nexus 7 reproduces the issue reliably - thanks a ton! Fix on it's way: http://crbug.com/360602 . -
@RickByers@ppk awesome diagnosis!
-
-
@Paul_Kinlan@ppk Found a race that may be related: https://code.google.com/p/chromium/issues/detail?id=360602 …, thanks for reporting issues!
Rick Byers
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.