>     Actually I just thought of a much better place to check it,
> add the above check to batik.gvt.UpdateTracker.changeStarted.
> I think that should catch all changes that could possibly
> cause trouble (which might include things like animations
> and CSS which the DOM checks might not catch), and it's just
> once place that you need to change...

Is this a general fix? That is, should the trunk benefit from this
thread's results or is this fix only meant to workaround a particular
situation?

Regards,

 Helder Magalhães

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to