The official release of Ext.NET Mobile is now available. Ext.NET Mobile is an ASP.NET component framework for building Phone and Tablet specific mobile web applications. Read More

[OPEN] [#1445] [4.2.0] Strange issue with Firefox 52 (UI freezes on some PCs also on Ext.Net examples...)

Page 1 of 2 12 LastLast
  1. #1

    [OPEN] [#1445] [4.2.0] Strange issue with Firefox 52 (UI freezes on some PCs also on Ext.Net examples...)

    We've experienced many times a strange issue with Firefox. Basically the app renders correctly, but mouse clicks DOES NOT WORK. The Keyboard seems to be working fine, ... but other interactions are "filtered" somehow.

    No errors appear on the console, ... and since the issue is not strange enough the issue is present ONLY on certain computers (not all) with the same version.

    We've seen that going to this link could help mitigating the issue but only for a short time,...

    ...but in a few days/weeks the issue comes back again and we're forced to reset again Firefox settings.

    The behavior can be reproduced on too!

    Is there any known issue with Firefox like this?
    Thank you for a feedback,
  2. #2
    Hello @adrianot!

    Yours the first report on these issues. Same version, different computers don't break? Seems an extensions or plug-ins issue. Something like that may be installed on the affected computers and triggering the error.

    Is it definitive? You can't interact with anything in Ext.NET pages? Or need to work on it a while before it stops responding mouse events? The random nature of the issue would make it rather difficult to pinpoint.

    Would safe mode help on the affected systems?
    Fabrício Murta
    Developer & Support Expert
  3. #3
    Hi Fabricio, yes, it looks like this ExtJS topic describes the issue:

    What do you think?
    Thank you!
  4. #4
    Yes! That's most definitely it! We are going to log it in our issues tracker too... Maybe something that forces isWebkit to be true on firefox 52 might mend the issue!

    But I upgraded Firefox to 52 here and the issue does not trigger... I get Ext.IsWebKit as false as stated in the Sencha thread, yet the examples works just fine. Did you find a definitive way to have Firefox 52 break? It seems just upgrading Firefox to 52 is not enough, there is something else that triggers and disables the mouse events handling.

    I have checked this comment which suggests how to fix... But I have the condition it says (dom.w3c_pointer_events.enabled = 2), yet firefox here works very well with Ext.NET. Any interaction like button clicks in this example should not work, right?

    It is not a question "is the problem there?", the question is "how to deterministically make firefox break with Ext.NET?"

    Without reproducing the issue our side we are helpless to suggest a workaround.
    Fabrício Murta
    Developer & Support Expert
  5. #5
    We have just logged issue #1445 to track this problem. If you have any hint on how to make devices that don't reproduce the issue actually reproduce it, let us know the steps to enable it so we can try an Ext.NET-side fix for this issue, at least for the time being.

    For now, I'm afraid the fix would be to disable w3c_touch_events on firefox as instructed in this mozilla comment.
  6. #6
    Can you reproduce the issue on this example:

    - Ext.NET 3 - buttons overview

    But this one works fine for you?

    - Ext.NET 4 - buttons overview
    Fabrício Murta
    Developer & Support Expert
  7. #7
    Hi Fabricio and thanks for the feedback.

    It appears you can reproduce the issue on any device with Firefox 52 forcing touch_events enabled also on devices that do not have them, like this:

    1) On the address bar of Firefox, put "about:config".
    2) Search the "touch" flag
    3) set the "dom.w3c_touch_events.enabled" to "1" instead of "auto-detect".

    Regarding the tests you asked me to perform with the settings above, the issue is present on both V3 and V4.

    Thank you!
  8. #8
    Yes, I tried all that on FF 52. At some point I seemed to be able to reproduce it on Ext.NET 3 example. Today tried again and they work. Even if I open fire bug, put in responsive design mode (equivalent to mobile emulation in chrome) and enable touch emulation.

    I tried both the config option and responsive design and the issue is not triggering with firefox 52.0 (32-bit). By chance you are using a 64-bit version of firefox? Can you double check that on firefox's about window?
    Fabrício Murta
    Developer & Support Expert
  9. #9
    Firefox 32-bit... :-( I tried enabling/disabling the feature and it switches between the two behaviors correctly). This configuration worked on customer computers too.
  10. #10
    Alright, I got it now!

    My dom.w3c_touch_events.enabled was 2 by default (or if I unset it). Wonder what 2 means...

    Setting it specificly to 1 breaks the examples even on v4.

    So, maybe if your customers having issues as they have touch devices and want to use them on FF (and setting that to 0 disables it), maybe setting it to 2 would let the users work with both touch hardware and mouse with FF and Ext.NET!

    Thanks for the feedbacks so far! Hope we can bring good news soon!
    Fabrício Murta
    Developer & Support Expert
Page 1 of 2 12 LastLast

Similar Threads

  1. Replies: 6
    Last Post: Feb 25, 2017, 3:51 AM
  2. Replies: 2
    Last Post: Apr 16, 2014, 3:56 PM
  3. bindStore() causes strange behavior in Firefox
    By thedarklord in forum 1.x Help
    Replies: 4
    Last Post: Nov 02, 2011, 8:39 AM
  4. Replies: 1
    Last Post: Sep 30, 2011, 11:15 AM
  5. [CLOSED] [1.0] Examples Viewer in Firefox
    By randy85253 in forum 1.x Premium Help
    Replies: 4
    Last Post: Nov 12, 2009, 4:17 AM

Posting Permissions