Databases
StackOverflow2013
Postsdbo
POPan/Zoom painfully slow in IE8 RaphaelJS
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POPan/Zoom painfully slow in IE8 RaphaelJS
    text
    copied!<p>I have been working on getting this seat mapping chart for a while and have created a few iterations, and the problem I keep finding is when I get to IE8 the panning for this is way to slow and delayed.</p> <p>What I have at this point to cut down on load time is created a png to replace my "strokes" since I assume ie8 wanted to re-render each time I dragged the map. </p> <p>I also added controls hoping to force IE8 users this option, but still there is a delay in the pan, and if I can have users with IE8 (and ie7 if possible) still drag/pan without the controls and the respond time a little faster that would be great.</p> <p><strong><a href="http://jsfiddle.net/knottAverage/ArKDp/29/" rel="nofollow">Here is my current JSFiddle</a></strong></p> <p>I am still a little green with JS so if you have any suggestions it would be much appreciated. (PS Chrome frame is awesome but <strong>is not</strong> a option for me)</p> <p><strong>Update</strong></p> <p>I have removed the original dragging function and replaced the code using jqueryui's draggable function. Martin had suggested to just drag the div, and not the Raphael elements. Doing so lets this thing fly in ie6-8 which is great, but then came my concern about scaling. What I was seeing before on zoom my paper element WxH would stay the same ratio, cutting off my drawing when it zoomed in. After digging through the Raphael documentation I came across paper.setSize. setSize was exactly what I needed to allow this project to move and groove in ie6-8 and pretty much conquer all browsers in its path.</p> <p>So in short, using jqueryui's draggable and paper.setSize has cured my cross browser zoom n' pan blues.</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload