Open fabriciomurta opened 7 years ago
Seems I cannot reproduce this here: http://examples4.ext.net/#/Buttons/Basic/Overview/
But I can reproduce the issue here: http://examples4.ext.net/#/Buttons/Basic/Overview/
So the bug does not affect Ext.NET 4.2.0.
The definitive way to make Firefox trigger the issue is:
about:config
w3c_touch_events
The same issue can be reproduced in Chrome if we load the page in mobile emulation mode (making it detect as a touch-driven browser), and then switch off mobile emulation (without reloading the page).
Steps to reproduce in chrome:
If at step 7 the page is refreshed, then it will work fine.
Update: Issue still open after ExtJS 6.5.0 release.
Update: Issue still open after ExtJS 6.5.1 release. Issue is acknowledged by Sencha under ID EXTJS-22720.
Update: Issue still open after ExtJS 6.5.2 release. Issue is acknowledged by Sencha under ID EXTJS-22720.
Update: Issue still open after ExtJS 6.5.3 release. Issue is acknowledged by Sencha under ID EXTJS-22720.
Update: Issue still open after ExtJS 6.6.0.258 release. Issue is acknowledged by Sencha under ID EXTJS-22720.
Update: Issue still open after ExtJS 6.7.0.161 release. Issue is acknowledged by Sencha under ID EXTJS-22720.
This issue has (very likely) been raised once again in this forum thread: Tablet with external keyboard (with touchpad).
Found: 4.2.0 Ext.NET forum thread: Strange issue with Firefox 52 (UI freezes on some PCs also on Ext.Net examples...) Sencha thread: Ext 6.2.0 don't listen mouse events when touch or pointer events are supported Mozilla issue 1: Enabling
w3c_touch_events
on desktop Firefox is causing major problems with ExtJS6 Mozilla issue 2 (older): ExtJS 6 not work on 52.0a2This comment (on the Mozilla issue 2) suggests which setting of FireFox should be enabled in order to trigger the defect: comment 20
It is claimed ExtJS 6 does not work at all with Firefox on touch enabled devices with also mouse (a computer with touch screen might be it, for example). During tests on my workstation, windows 8.1, upgraded Firefox to 52, the
dom.w3c_touch_events
is different than 0 (it is 2) and the claimed behavior does not happen.Also tried responsive design mode (on firebug) with touch emulation enabled as suggested by the comment right after comment 20 above, but couldn't reproduce the issue as well. The examples explorers seems to work fine no matter what, even though the claimed requirements are all met.
Firefox tested is Firefox 52.0 (32-bit).