Change
Improve touch only detection
Issue description
After upgrading to buster, chromium was behaving like a touch device. Firefox was not. This behavior is activated when the browser "w.matchMedia("(hover: none)").matches" evaluates to true, which means the browser does not consider itself to be capable of hover. Evidently this is wrong.
Developer comments
On the first eligible mouse move event, Topincs stores this insight in sessionStorage and considers it valid from there on. It does not revisit the determination process. Yes, that might cause problems in other circumstances (unplugging the mouse), but these are less frequent.
|
Work sessions
Start |
2021-09-08T13:45:33
|
End |
2021-09-08T15:45:40
|
Participant |
Robert Cerny
|
|
We are sorry
This page cannot be displayed in your browser. Use Firefox, Opera, Safari, or Chrome instead.