Bug Report Q479418
Visible to All Users

DXTREME, JavaScript error - 'WebKitCSSMatrix' is not defined

created 12 years ago

After update my Dxtreme for the issue (http://www.devexpress.com/Support/Center/Question/Details/Q476624), I create new projects and try navigate another view in the IE or Firefox causes error:

0x800a139e - Erro em tempo de execução do JavaScript: SyntaxError
The program '[1492] iexplore.exe' has exited with code 259 (0x103).
-------------------------

Unhandled exception at line 9, column 12345 in http://localhost:64546/js/dxtreme.core-12.2.js

0x800a1391 - Erro em tempo de execução do JavaScript: 'WebKitCSSMatrix' não está definido

Comments (1)
DevExpress Support Team 12 years ago

    Thank you for pointing us to this issue. I have passed this ticket to our R&D team for research. Please bear with us, we will get back to you as soon as possible,

    Answers approved by DevExpress Support

    created 12 years ago (modified 12 years ago)

    We have fixed the issue described in this ticket and will include the fix in our next maintenance update. To apply this solution before the official update, request a hotfix by clicking the corresponding link for product versions you require.

    Note: Hotfixes may be unavailable for beta versions and updates that are about to be released.

      Show previous comments (3)

        At the moment to proceed with development I modified the dxtreme.core-12-2.js:
        _createTransformStrategy: function () { return /*t.support.transform3d*/ false ? new t.fx.Transform3DTransformStrategy : new t.fx.CssTransformStrategy }
        Can the problem be related to upgrading IE to version 10 ? (Windows update intalled it this morning on my W7 pc)

        DevExpress Support Team 12 years ago

          It appears that in some scenarios it is not sufficient to switch off that single option. The complete workaround should be a bit more complex:

          JavaScript
          if(!('WebKitCSSMatrix' in window && 'm11' in new WebKitCSSMatrix()) && DevExpress.support.transform3d) { DevExpress.support.transform3d = false; DevExpress.fx.currentAnimator = new DevExpress.fx.Animator(); DevExpress.fx.animate = $.proxy(DevExpress.fx.currentAnimator.animate, DevExpress.fx.currentAnimator); DevExpress.fx.transform = $.proxy(DevExpress.fx.currentAnimator.transform, DevExpress.fx.currentAnimator); DevExpress.fx.setProp = $.proxy(DevExpress.fx.currentAnimator.setProp, DevExpress.fx.currentAnimator); DevExpress.fx.getProp = $.proxy(DevExpress.fx.currentAnimator.getProp, DevExpress.fx.currentAnimator); }

          Please accept our apologies for the inconvenience. I have removed the incorrect suggestion from the answer section and suggest that you wait a bit for the public fix. It will be available very soon.

            It works!

            Disclaimer: The information provided on DevExpress.com and affiliated web properties (including the DevExpress Support Center) is provided "as is" without warranty of any kind. Developer Express Inc disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.

            Confidential Information: Developer Express Inc does not wish to receive, will not act to procure, nor will it solicit, confidential or proprietary materials and information from you through the DevExpress Support Center or its web properties. Any and all materials or information divulged during chats, email communications, online discussions, Support Center tickets, or made available to Developer Express Inc in any manner will be deemed NOT to be confidential by Developer Express Inc. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.