jQWidgets Forums
Forum Replies Created
-
Author
-
February 25, 2016 at 8:26 am in reply to: jqx-all.js runtime exception: Uncaught TypeError: (…) is not a function jqx-all.js runtime exception: Uncaught TypeError: (…) is not a function #81822
Hi,
is there an progress? I face the same issue since I’ve updated to version 4 and I can not use the minified because of I need to debug.
June 18, 2015 at 3:04 pm in reply to: Crash in jxq.data.export v3.8.0 / ie8 Crash in jxq.data.export v3.8.0 / ie8 #72692Hi,
Unfortunately, I can’t put a <script> tag in a try catch…
We have many customers using ie8 and I can’t tell them that the issue is a ‘normal’ situation.
AlainJune 18, 2015 at 12:57 pm in reply to: Crash in jxq.data.export v3.8.0 / ie8 Crash in jxq.data.export v3.8.0 / ie8 #72687Hi,
I tested on a genuine ie8 AND on an emulated ie8 on ie10.
Just create a simple html page and add the followings:<link rel="stylesheet" href="../../Libraries/jqwidgets3.8.0/styles/jqx.base.css" type="text/css"/> <script src="../../Libraries/jQuery/jquery-1.10.2.js"></script> <script type="text/javascript" src="../../Libraries/jqwidgets3.8.0/jqx-all.js"></script>
You will get the following message:
L’objet ne gère pas la propriété ou la méthode « createElementNS »
Which means something like “object does not handle the property or method « createElementNS »”
Do you need more info?Best regards,
June 18, 2015 at 12:28 pm in reply to: Crash in jxq.data.export v3.8.0 / ie8 Crash in jxq.data.export v3.8.0 / ie8 #72685Thanks for your quick answer.
The crash occurs when including jqx.data.export.js in our application.
I’ll try to reproduce it in a separate app and come back to you ASAP.
FYI, previous versions of the file did not use createElementNS.
Best regards,
AlainMarch 26, 2015 at 3:48 pm in reply to: crash due to a change to native JavaScript Array object crash due to a change to native JavaScript Array object #69196Peter,
I am a bit surprised by your answer.
A simple solution is to add test within the loop with ‘hasOwnProperty’ which is considered as a good practice in JavaScript programming (every for (prop in obj) loop should use this test. cf. “Removed Link”“It is wise to program defensively by using the hasOwnProperty method to distinguish the true members of the object:…”
Adding this test won’t have any impact on the normal behavior of the control and none of your users will see any difference.
We use many of your components and the charts are the only ones to be impacted. Honestly, it’s worth making this small change, don’t you think?Regards,
Alain
In my case, that.width is a number and
(25).indexOf(“%”) ===> TypeError: undefined is not a function
Maybe it’s not a bug but il looks like un bug …
It works after correction
toString() of course
-
AuthorPosts