3 ms·
This terrible slowness in IE with flot is because IE doesn't support the <canvas> tag, so it has to be simulated in javascript. In Firefox and Chrome Flot uses
by benmathes 17y ago
This terrible slowness in IE with flot is because IE doesn't support the <canvas> tag, so it has to be simulated in javascript. In Firefox and Chrome Flot uses the <canvas> tag, and therefore native browser code, to do the drawing.
- gruseom 17y agoThat's precisely why the only acceptable way to do this is with VML on the IE side. VML is surprisingly good for something so old. It's essentially SVG avant la lettre. Its main problem is that it's very poorly documented.
- donalm 17y agoFlot requires excanvas.js to simulate the canvas in IE. Internally excanvas.js uses VML.
- gruseom 17y agoI said that an acceptable solution would have to use VML, not that a VML solution would have to be acceptable. The Canvas API is completely dissimilar to VML, so it's not surprising that excanvas et. al. have proven to be notoriously slow. It's not clear to me why anyone would even bother, except as a way to bolt IE support on as an afterthought. Like it or not, anything that does that is going to be commercially marginal. As I mentioned, VML is remarkably close to SVG. So there's an obvious solution here.