Changes between Version 1 and Version 2 of Ticket #17810, comment 14


Ignore:
Timestamp:
May 22, 2014, 3:30:33 PM (6 years ago)
Author:
Sebastien Brunot
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #17810, comment 14

    v1 v2  
    1 The current fix, as discussed with spereira, has a side effect: because Chrome 35 (at least on iOS) do implement maxTouchPoints in the navigator object but do not implements pointer events, dojo/touch is broken on this browser: it listens to pointer events that are never emitted.
     1The current fix, as discussed with spereira, has a side effect: because Chrome 35 (at least on mac OS X) do implement maxTouchPoints in the navigator object but do not implements pointer events, dojo/touch is broken on this browser: it listens to pointer events that are never emitted.
    22
    33You can test that with the two following dojo mobile tests, that are failing on Google Chrome 35: