https://issues.apache.org/bugzilla/show_bug.cgi?id=48561
--- Comment #4 from Helder Magalhães <[email protected]> 2010-01-25 16:15:13 UTC --- (In reply to comment #3) > Not sure what you mean by the demo containing the batik-gui-util - certainly > not the one in my cache!!! 8-) Yup, you are right. My bad. I guess the demo wasn't made to handle errors but more towards being simple and download friendly. ;-) > But I take your point. > > I'm capturing the event, changing the host page's location and stopping the > applet to prevent the error wherever possible (it still seems to cause the odd > exception on disposal but hey) So I guess it should be ruled out as a bug - > surely though there should be a silent/console only error reporting flag or > similar - my users would think they had a virus if they saw exceptions like > that. Thing is, SVG's error processing [1] states that the object should stop rendering whenever an error occurs and stuff like that, which makes it necessary to warn the author/user whenever bad content is detected; else the user might be tricked into a situation where he feels that everything is as expected when it may not even have completely loaded! (Imagine a broken script, for example). So the errors in your case are probably just content errors. I'd ask (again) that you'd confirm that and, if the errors are unexpected, to attach test cases to this bug. > So I guess the bug is simply the absence of the jar in the demo page! I'm not sure, given that it's a demo (i.e., "batik-gui-util.jar" is not even there). I'm considering building a wiki page with more information on how to assemble a standard Batik-based applet, though... ;-) Does keeping this issue open still makes sense? [1] http://www.w3.org/TR/SVG/implnote.html#ErrorProcessing -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
