Open dascritch opened 3 years ago
This problem seems only occurring on Android Chrome, not on iOS. But manual interaction is conform.
I suppose this is due to a different mouse event management. I've toyed 580890787ab3a031729cdd9121a91d2b06d527d4 gut got nothing
This test is simple, but has a very strange bug only on Chrome Android : It seems related to the way on this platform Google integrated the mouse API. Because, yes, since the very first Chrome, you can attach a mouse on your phone and use a cursor ! May be should I instead use pointer events, as they are now enough supported https://caniuse.com/pointer
The bug is still here. We cannot resolve it by our side, so, removing it from the release objective.
“Click at the middle of the timeline” is supposed to respond a timecode at 1:00 ± 0.1s
The test give strange results : 0:56 or 0:16 depending the width of the screen. Firefox on Android and desktop give correct results. It may come to a specific implementation on Chrome Android. Test must be rewritten.