Highcharts not rendering in IE 11 - javascript

I am using Highcharts JS v2.2.5. It works fine in all browser except IE 11. I am able see the data but, Chart is not rendering.

Do you have already excluded for wrong position or zero-height container? it's a common bug..
We need to know more details, can you post some code?
Have you any error evidence in browser console?

If you are using prototype.js version 1.5.1.1 then there is a possibility of getting error in console[on hover function] only in IE[All versions]. If this is the issue then it can be solved by using higher version of prototype.js

Related

What is the problem with D3js working with Internet explorer 11

I am creating an SVG donut chart using D3js v4 library, and it works fine with Google chrome but it doesn't work at all with IE11
I tried to to put the code in this Codepen
'https://codepen.io/ohmto/pen/eYZeYqW'
any help or a reason why it doesn't work on IE11, it will be appreciated
I try to check your code and found => arrow functions in it. Arrow functions are not supported in the IE browser.
I try to modify your sample code and try to convert the arrow functions to normal functions to make it work with the IE browser.
After modifying the code, I noticed that the chart getting created but it is not in the proper format and data are missing too.
output in the IE 11 browser:
I again try to modify the JS and CSS code but the result was the same.
Further, I try to check the D3.JS and SVG related documents.
You can notice that SVG has partial support in the IE browser.
Some parts of D3.js may also not work with the older browsers.
You can try to simplify your sample and check whether it works with the IE. If it does not work then I suggest you use the JS code to identify the browser and inform users to visit the site using compatible browsers for your site.

Hierarchical layout with vis.js

I'm using vis.js library to graphically display a network. I read the documentation and I need to use the hierarchical layout. It works fine until I use the sortMethod='directed' option. In this case I end up with a blank page. There's no Javascript error. Every other options combination works fine, but I need the directed option. I followed the documentation and it doesn't seem that I need to add further information to the network: it should all work with the 'from' and 'to' edges properties. What could it be?
Thank you all.
It seems to be a bug. I have been using this feature for months and suddenly it stopped working. I get the same behaviour as the one you describe. All options seem to work except the sortMethod='directed'. I cannot tell for sure which version introduced this bug but I found it out at 4.12.0.
We probably need to raise an issue to let their dev team know about it.
Hope that helps. It is not exactly a solution to your issue but rather a verification of this bug since I have the same issue.
EDIT:
I tried both 4.11.0 and 4.10.0
4.11.0 : I get the same buggy behaviour.
4.10.0 : Works as expected. No issues.

Uncaught TypeError ONLY in Chrome

I#ve a very strange problem calling a simple function in JavaScript.
Just for example, even a simple:
click
or:
click
gives me an Uncaught TypeError: object is not a function.
But ONLY in Chrome and ONLY on my Notebook. On my Workstation (same system, exactly same Chrome Version) and in every single other browser this line works as expected.
Im Working with JS since a few years, but this error drives me nuts since days.
The Website comes with scriptaculous and some handwritten JS, but nothing really special.
scriptaculous works well, JS-Console shows no errors except the one #Chrome on my Notebook.
Anyone of you ever had this before?
I#ve really no idea whats going on.
My suggestion is to assign it via javascript and not like an inline attribute. Sometimes you get odd behaviour setting it as an attribute.
You could use jQuery:
jQuery('.myClickableLink').click(function(){ alert(123) })
I think that's a simpler way.
I am betting you have a pop up blocker installed on that machine that hijacks window.alert. Disable the plugins and see if it works correctly. [Normally a pop up blocker does this]
use
window.alert('msg)';
it will work...

JQgrid not sizing properly in IE8

For some reason I cannot seem to get IE8 to display my jqgrid right as you can see below. This isn't the only grid that doesn't display properly. I have another one in my project that renders just like the one below :(. Needless to say, I tried all sort of column widths, tried turning the scrollbars off etc etc. but nothing seems to improve the situation.
Am I missing something obvious ?
I am using the very latest JQgrid version 3.8.
Firefox:
Explorer:
Mostly the problem exist in CSS which you use (for example standard CSS generated by ASP.MVC MVC). Different web browsers interpret CSS inheritance differently. Look at this answer and this. Probably the usage of increased cellLayout parameter or the function fixGridWidth inside of loadComplete could solve your problem.

magento bundle.js error

I just discovered on my site using magento 1.3.2.2 that on a bundled product, when adding different options the price does not change in internet explorer. It works fine in all other browsers however.
In internet explorer I get the error message.
Message: Object doesn't support this property or method
Line: 34
Char: 9
Code: 0
URI: /skin/frontend/my_new_interface/design2/js/bundle.js
So I checked out line 34 and found
parts = selection.id.split('-');
I verified that selection.id is a string. I'm not a javascript expert and I'm not familiar with prototype.
On a lark I decided to split up the line as:
var parts = selection.id;
parts = part.split('-');
Well that fixed the problem. Furthermore I went back and just reduced to:
var parts = selection.id.split('-');
Which still worked as well. I don't think this is a file I should be messing with though. I'm assuming this javascript class should work fine in ie without me having to change anything.
I'm hoping someone has an idea of why this might have fixed the problem or what I can do to find out what the real problem is. Do you see any problem with me leaving this fix the way it is?
It's very possible that you hit an ID in the other case that didn't exist, and therefore it was attempting to split an undefined variable. If the fix works for you, stick with it, but you may want to consider upgrading your Magento installation. The series is onto 1.4 now, and there are huge numbers of fixes in every release.
Hope that helps!
Thanks,
Joe

Categories