that makes some sense, but if it were the case, why wouldn't Firefox jump
too?
perhaps we'll have to wait for Brice...
Brian Cherne wrote:
>
> It's hard to read Brice's minimalist (elegant and light) code style... but
> I
> suspect the reason it's breaking is on line 27:
>
> var f=function(w,t){return parseInt(w.css(t)) || 0};
>
> If w.css returns undefined then your value will be 0 initially. If w.css
> is
> a percentage, then it will think 10% is really 10px. In either case you're
> likely to see a jump.
>
> (Note: I haven't confirmed this as the culprit, but it seems the most
> likely
> suspect at this time.)
>
> It will require a little extra work to convert the % into a px value
> before
> being used. Essentially you'll need to determine the object's x/y
> coordinates instead of reading in the style.
>
> Brian.
>
>
--
View this message in context:
http://www.nabble.com/jqDnR-%2B-jqModal----dragging-causes-jump-in-IE---Safari-tf4014648s15494.html#a11423212
Sent from the JQuery mailing list archive at Nabble.com.
