Up until now I had a well functioning interactive graph on a page rendered using flot. After some patches were pushed, it stopped rendering in IE7. After some trial and error I found that neither flot, nor any other js drawing library (that used excanvas or some derivative for IE fallback) would render on IE7 or IE8 on Windows XP with KB2482017. Windows 7, IE8 with the patch is not affected. I have not tested Vista.
After some digging it seems even basic VML is broken on XP with the patch. Microsoft's own VML sample fails to render.
Has anyone else seen this behavior, and if so, know a workaround?
Here is a screenshot of my reputation graph from a machine with XP, IE7, and the patch applied.
Do you have McAfee antivirus, with HIPS 7.0 ? If so that could be the cause.
Check https://kc.mcafee.com/corporate/index?page=content&id=KB70810 for a similar issue.
Related
I am taking webpage screenshot of svg content using canvg. In Chrome, Opera and IE11 it seems to work fine, however in Edge browser it only weirdly renders black background with no content on the canvas.
Try it here in Edge browser
Open the link above and try the following examples
1) soccer
2) floorplan
I am unable to find the problem. Apparently looks like Edge is not supported by canvg. I hope someone already found a solution for this. It will be a great help!
There's more information about this issue here: https://github.com/canvg/canvg/issues/520
There is currently a merged PR that has not been released as mentioned in the issue and there's a workaround by monkey patching the code from that fix into the canvg code. You may want to subscribe to that issue so you know when the patch is released.
I implemented LeafletJS 0.8 in my application. This because of the many bugfixes I needed. However It seems that zooming is not working as expected in IE11
The leaflet is zooming out of its bounds, only in IE11
For a demo see here: http://robballou.com/j/leaflet.php?leaflet=8
Does anyone has an idea what could be happening here?
You do not have to provide valid code, just a point in the right direction would already be very helpful.
Edit: I just tested this on a Windows 7 machine and there are no problems there. It just happens on Windows 8 apparently
Unfortunately, this looks like an IE bug introduced when we added additional hardware accelerated composition in IE for Windows 8 and above. Sorry about that! I've filed a bug for us to investigate: https://connect.microsoft.com/IE/feedbackdetail/view/1085713/transformed-elements-appear-outside-map-extents-in-leafletjs-win8-only
If during our investigation we find an easy workaround for you, I'll come back and post it here.
I'm working on a project via arcgis javascript api.
With hundreds of graphics drawn on a graphicsLayer, it works well on chrome or IE11, but on IE8 and supposedly also IE6 when I drag the map, it's extremely slow so that makes it completely unusable.
I found the "displayOnPan" option of graphicslayer which seems to be designed specifically for IE. But if I turn that off, the performance is still unsatisfactory, besides, the disappearing and reappearing of the graphics each time the map is panned are really irritating.
No question of requiring the users to update or change the browser.
Is there any ways to the problem?
According to ESRI, no. This is what I got from ESRI's support centre when I put the same question to them
Hi Clark,
The Javascript API support for Internet Explorer 9 introduced significant performance improvements for drawing graphics.
In earlier versions of Internet Explorer, drawing large number of graphics performed poorly compared to browsers like Firefox and Chrome. At IE9, graphics drawing performance is much improved over earlier versions of IE and is comparable to other browsers.
A table comparing performance between the different browsers is available at https://developers.arcgis.com/javascript/jshelp/new_v23.html
Feature services are essentially graphics. If the layer(s) you're loading contain a large number of features, this is the reason for slow performance in IE8.
I'm interested in finding a browser compatibility table that lists the parts of SVG/VML supported by each version of Opera, Safari, Chrome, Firefox and Internet Explorer (also Konqueror would be nice) in the vein of Quirksmode.
I have found the following two compatibility tables for SVG but neither of them provide enough detail:
http://caniuse.com/#cats=SVG&statuses=rec
http://www.codedread.com/svg-support.php
The information in the first link seems to clash with libraries like Raphael which claim to fully support animations in Firefox 3.0+ and Safari 3.0+ whilst the link suggests that the animation module isn't implemented till later versions for those two browsers.
The second link simply doesn't go far back enough for me to be able to draw conclusions about which features of SVG/VML I can use to ensure compatibility with older browsers.
Needless to say I'm endlessly confused.
To be perfectly clear, I'm interested in finding out which part of SVG are supported in different versions of all the popular browsers. As IE doesn't support SVG I'm interested in finding out which parts of VML the are supported in the different versions of IE.
If the developers of the libraries have found this information it must exists, it just seems to be evading me.
Any help would be much appreciated.
You may find this article helpful:
Creating SVG vector graphics for maximum browser compatibility
http://voormedia.com/blog/2012/10/creating-svg-vector-graphics-for-maximum-browser-compatibility
It shows some good examples of SVG features which aren't even supported by the latest versions of Chrome.
There's also a nice compatibility table at the bottom.
flot v0.5 fails to render correctly in IE8 RTM. I am using excanvas library that comes packaged with flot (as per instructions).
The project description states that IE8 is supported but doesn't mention which mode (compat or standards).
Does anyone have experience using flot v0.5 with IE8?
Thanks
I just tried loading the Flot examples in IE 8. It only worked when I enabled the compatibility view button which suggests it is only known to currently work in compatibility mode.