Details
-
Bug
-
Status: Open
-
Resolution: Unresolved
-
1.8
-
None
-
None
-
Operating System: Windows Vista
Platform: PC
Description
While participating in a batik-users thread [1], I discovered a set of (minor?) issues while playing with Batik Squiggle's DOM Viewer. I'm creating this bug in order to 1) act as a reminder to try better tracking them down whenever possible and 2) act like a list of known-issues in case someone else also happens to bump at something weird while using the DOM viewer.
Maybe this could/should be broken into several bugs (one per issue) but, given that these issues should be fairly to fix, managing multiple issues can become too much of a burden (as already discussed a couple of times in batik-dev). 
1. Works with simple cases [1], seem to choke with more complex ones [2].
Nevertheless, in the second test case, I'm also seeing unresolved namespace weirdness (the "a0" hints towards that)which I thought it had already been fixed in trunk:
<a0:g xmlns:a0="http://www.w3.org/2000/svg" style="fill: #ffffff; stroke:#000000; stroke-width:0.172">
<a0:path d="[long path data]"/>
</a0:g>
I still haven't figured out if this is due to:
- [3] being a more complex document;
- [3] making heavy use of cubic splines, which may be breaking the node finder/highlighting algorithm.
2. The DOM viewer doesn't maintain state: whenever the (DOM Viewer) window is closed and opened again, the previously highlighted items are disconnected. The simplest approach would be clearing the set of highlighted items prior to closing the window; another possibility would be maintaining state, for example by hiding the window instead of closing it (not sure about the performance implications of that).
Both issues were noticed in revision 892855, using Sun Java 1.6 update 17 on Windows Vista SP2.
[1] http://old.nabble.com/background-for-text-td26879322.html
[2] http://heldermagalhaes.com/stuff/svg/demos/SVGObject-HTMLCanvasInteractors/sample.svg
[3] http://croczilla.com/bits_and_pieces/svg/samples/tiger/tiger.svg