Page 3 of 3 FirstFirst 123
Results 21 to 28 of 28

Thread: Examples don't work in Firefox 52 + touchscreen

    Success! Looks like we've fixed this one. According to our records the fix was applied for EXTJS-23846 in 5.1.5.
  1. #21
    Sencha - Support Team keckeroo's Avatar
    Join Date
    Mar 2008
    Location
    Winnipeg, Canada
    Posts
    387

    Default

    Hi,

    This isn't a bug in the true sense of the word. This is an incompatibility with FF52, a client which was released *after* the release of the framework versions mentioned in this thread.

    We will always do our best to address issues that appear in newly released browsers, and provide (where possible) a temporary fix until this can be addressed in future releases of ExtJS. Respectfully, just as we test our framework for stability and functionality on available browsers before release, it behooves our customers to take the same steps when they wish to upgrade their browsers. It is neither wise nor advised to upgrade browsers without just cause, especially if your application is currently running without incident.

    It's always recommended to test your application on any new browser before attempting to upgrade browsers in a production environment. Report any issues to us, should any be found, and we can mitigate these problems and provide work arounds before you find yourself in a situation where you have a production environment that no longer functions correctly.

    With respect to this FF release, we are continuing to receive reports of other issues and they are being addressed as best as possible.

    Regards,

    Kevin Cassidy
    Sencha Support Team

  2. #22
    Sencha Premium Member tjstuart's Avatar
    Join Date
    May 2007
    Location
    Sydney, Australia
    Posts
    457

    Default

    Quote Originally Posted by keckeroo View Post
    It is neither wise nor advised to upgrade browsers without just cause, especially if your application is currently running without incident.

    It's always recommended to test your application on any new browser before attempting to upgrade browsers in a production environment.

    You are assuming we have control over when or if a end user web browser updates. This is nonsensical. Those that have paid for maintenance and support expect that the vendor (Sencha) does basic QA on future browsers, this is one of the reasons we pay you for the software. Both FF52 and Chrome 56 introduced major breaking bugs, where was your QA here? What of Sencha Test? Or do you not eat your own dog food?

  3. #23
    Sencha User
    Join Date
    Mar 2017
    Posts
    2

    Default

    Quote Originally Posted by keckeroo View Post
    It is neither wise nor advised to upgrade browsers without just cause, especially if your application is currently running without incident.
    https://www.mozilla.org/en-US/securi...ities/firefox/
    Enough good causes maybe? The rest of your statement is understandable but regular upgrades of especially web related software are mandatory. It's neither helpful nor accurate using such a phrase to lecture people which support your software by reporting bugs or incompatibilities.

  4. #24

    Exclamation

    Where can I put this code¿? On launch function¿? I´m using Sencha Architect and my buttons click don't work in Firefox 52 (desktop)

    // Undo sencha's logic // Needed for top nav buttons to not open links in new tabs/windows when clicked in IE11 EXTJS-13775
    // Firefox 52 is getting deteceted now as ALWAYS having pointer events
    // chromeOS causing issues too
    // unit tests failing
    if (Ext.isIE || Ext.isEdge || (Ext.firefoxVersion >= 52) || Ext.os.is.ChromeOS || window.inUnitTest) {
    // sorry windows mobile phones...
    var eventMap = Ext.dom.Element.prototype.eventMap;
    eventMap.click = 'click';
    eventMap.dblclick = 'dblclick';
    }


  5. #25
    Sencha Premium User alexander.urban's Avatar
    Join Date
    Nov 2013
    Posts
    324

    Default

    Quote Originally Posted by tjstuart View Post
    You are assuming we have control over when or if a end user web browser updates.
    I guess that since the ExtJS framework is now directed mostly at Enterprise for their intranet apps and dashboards (compare licensing minimum seats, compare dashboard examples), they expect that the admins have control over the browsers of the end users. But then, IE 11 and servers with compatibility mode set via GPO still aren't supported, although this setting will occur in many enterprises.

    So right now I am not so sure what the intended target audience of ExtJS is at all.

  6. #26
    Sencha Premium Member
    Join Date
    Sep 2014
    Location
    Graz
    Posts
    21

    Default

    Quote Originally Posted by keckeroo View Post
    Hi,

    This isn't a bug in the true sense of the word. This is an incompatibility with FF52, a client which was released *after* the release of the framework versions mentioned in this thread.

    We will always do our best to address issues that appear in newly released browsers, and provide (where possible) a temporary fix until this can be addressed in future releases of ExtJS. Respectfully, just as we test our framework for stability and functionality on available browsers before release, it behooves our customers to take the same steps when they wish to upgrade their browsers. It is neither wise nor advised to upgrade browsers without just cause, especially if your application is currently running without incident.

    It's always recommended to test your application on any new browser before attempting to upgrade browsers in a production environment. Report any issues to us, should any be found, and we can mitigate these problems and provide work arounds before you find yourself in a situation where you have a production environment that no longer functions correctly.

    With respect to this FF release, we are continuing to receive reports of other issues and they are being addressed as best as possible.

    Regards,

    Kevin Cassidy
    Sencha Support Team
    Is this some sort of a joke? Because it has to be a joke. How can we control our clients browsers on production?

  7. #27

    Default

    Create onRender function on viewport::

    onRender: function() {
    //Bug Firefox
    // Undo sencha's logic
    // Needed for top nav buttons to not open links in new tabs/windows when clicked in IE11 EXTJS-13775
    // Firefox 52 is getting deteceted now as ALWAYS having pointer events
    // chromeOS causing issues too
    // unit tests failing
    if (Ext.isIE || Ext.isEdge || (Ext.firefoxVersion >= 52) || Ext.os.is.ChromeOS || window.inUnitTest) {
    // sorry windows mobile phones...
    var eventMap = Ext.dom.Element.prototype.eventMap;
    eventMap.click = 'click';
    eventMap.dblclick = 'dblclick';
    }
    }


  8. #28
    Sencha Premium Member
    Join Date
    Sep 2014
    Location
    Graz
    Posts
    21

    Default

    the examples are again not working, but now the scroll does not work with mouse when a touchscreen is connected (we had this problem for couple of months, but could not fix it)

Page 3 of 3 FirstFirst 123

Similar Threads

  1. Replies: 1
    Last Post: 9 May 2014, 12:56 PM
  2. Replies: 0
    Last Post: 1 May 2012, 7:05 PM
  3. Terminal TouchScreen Applications
    By davisty in forum Sencha Touch 1.x: Discussion
    Replies: 7
    Last Post: 11 Feb 2011, 1:47 PM
  4. ExtJS and Touchscreen Devices
    By Jaitsu in forum Community Discussion
    Replies: 11
    Last Post: 17 Jun 2010, 3:38 AM
  5. ExtJS and touchscreen
    By Stephan123 in forum Ext 3.x: Help & Discussion
    Replies: 11
    Last Post: 4 Sep 2009, 9:04 AM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •