You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
I've developed a little app in Javascript that allows someone to pan and zoom around.
I'm using Raphael to draw bezier paths, underneath absolute DIV's that hold images.
The user is able to navigate through different data using a next button. What happens when you hit next is that it removes all the old stuff on the paper and then add the new data.
This works great on SVG browsers. However, i've noticed that while using IE8, so VML, if the viewBox has an x,y, offset, after I have added the new paths, they are placed with an offset equivelent to about half of the viewBox x,y offset. This makes them offset to my absolute DIV's.
Again this is fine using SVG browsers. I initially thought that it was a problem with my code, however, I found a way to fix the offset so everything remains syncronized.
To fix it I have to return the viewBox to position 0,0 and the origianl width and height before I add the new paths, then recaculate panning and zooming, then everything works fine. I can only conclude that this is a Bug :)
Regards,
The text was updated successfully, but these errors were encountered:
Hello,
I've developed a little app in Javascript that allows someone to pan and zoom around.
I'm using Raphael to draw bezier paths, underneath absolute DIV's that hold images.
The user is able to navigate through different data using a next button. What happens when you hit next is that it removes all the old stuff on the paper and then add the new data.
This works great on SVG browsers. However, i've noticed that while using IE8, so VML, if the viewBox has an x,y, offset, after I have added the new paths, they are placed with an offset equivelent to about half of the viewBox x,y offset. This makes them offset to my absolute DIV's.
Again this is fine using SVG browsers. I initially thought that it was a problem with my code, however, I found a way to fix the offset so everything remains syncronized.
To fix it I have to return the viewBox to position 0,0 and the origianl width and height before I add the new paths, then recaculate panning and zooming, then everything works fine. I can only conclude that this is a Bug :)
Regards,
The text was updated successfully, but these errors were encountered: