Announcement

Collapse
No announcement yet.
X
  • Filter
  • Time
Clear All
new posts

    Grid not working after upgrade to FireFox 49

    We are using v10.1p_2016-03-18/PowerEdition. In firefix 47, everything is working correctly. Once I upgrade to FireFox 49, the grid stops working and I see this stack trace:

    Code:
    *19:31:56.853:WARN:Log:TypeError: isc.isA.DataSource is not a function
    Stack from error.stack:
        ClassFactory._defineClass()
        ClassFactory._defineNonRootClass()
        ClassFactory.defineClass()
        unnamed()
    ISC_Core.js:1078:137
    *19:31:56.862:WARN:Log:TypeError: isc.ImgTab.getPrototype is not a function
    Stack from error.stack:
        unnamed()
    ISC_Core.js:1078:137
    *19:31:56.906:WARN:Log:TypeError: _2.getPrototype is not a function
    Stack from error.stack:
        ClassFactory._mixInProperties()
        ClassFactory.mixInInterface()
        ClassFactory._defineClass()
        ClassFactory._defineNonRootClass()
        ClassFactory.defineClass()
        unnamed()
    ISC_Core.js:1078:137
    *19:31:56.947:WARN:Log:TypeError: isc.DateGrid.getPrototype is not a function
    Stack from error.stack:
        unnamed()
    ISC_Core.js:1078:137
    *19:31:57.005:WARN:Log:TypeError: isc.StatefulCanvas is undefined
    Stack from error.stack:
        unnamed()
    ISC_Core.js:1078:137
    *19:31:57.043:WARN:Log:TypeError: isc.SimpleScrollThumb is undefined
    Stack from error.stack:
        isc.loadSkin() @ /CRMApp/isomorphic/skins/SafetyNetSkin/load_skin.js:56:13
        unnamed() @ /CRMApp/isomorphic/skins/SafetyNetSkin/load_skin.js:1739:1
    ISC_Core.js:1078:137
    *19:31:57.160:WARN:Log:TypeError: isc.ListGrid.addProperties is not a function
    Stack from error.stack:
        isc.ApplyAutoTestMethods()
        anonymous()
        [c]Page.handleEvent()
        [c]EventHandler.handleLoad()
    I found a similar issue from a few months back:
    http://forums.smartclient.com/forum/...=1477611752073

    What is the next patched version that this issue was resolved in? I am hesitant to take the latest as we are in the last week of certification and I do not want to introduce regressions (either bugs or changes to functionality). Was the change a simple one liner that perhaps I can patch myself with our current version?

    #2
    The fix should have appeared in the nightly builds dated 2016-08-04 and beyond - several branches appear to have builds currently available dated 2016-08-05 or 2016-08-06 so those should address it.

    Comment


      #3
      Thanks...Per my original post I am hesitant to take 5 months of updates and apply to my production deployment as this has caused issues in the past...either from regressions or change in functionality is it possible to patch our current build or tell us the change so we can apply it manually?

      Comment


        #4
        No, sorry. We do not supply individual patches because this creates a combinatoric explosion of possible test configurations.

        Applying other recent fixes just means less issues to possibly encounter in the future.

        Comment

        Working...
        X