> > The problem is that, when I try this document in batik, the color of
> > the shape changes even when the cursor is over the non-apparent part
> > of the circle: The cursor is outside the rectangle, but would be on
> > the circle if it wasn't "clip-pathed", and the part of the circle
> > inside the rectangle changes its color.
> I guess the specification isn't clear enough regarding this. See bug
> 46289 , which contains a patch by Thomas to "fix" it and also links
> to relevant discussions in the www-svg mailing list. :-)
Please read the svg mailing list to understand the complexity of the
> > So I would like to know if it's a bug of batik? Will it be fixed?
> I'm not sure if the patch will be integrated. I'd vote for so,
I would vote no...
> but I remember the discussion somehow hit a dead end: there was no clear
> consensus at the time... :-( Maybe this is addressed in the second
> edition of the SVG 1.1 specification. :-)
The spec needs to be updated and until that happens I'm against
changing Batik's behavior only to have to change again when the Spec
is updated (causing problems for authors that need functionality around
> As stated, in order to "fix" it you may locally apply the patch
> already referred. ;-)
You can also use an invisible 'blocker' element in addition to
the clip to intercept the unwanted events.
> As stated within the www-svg debate, another way of working around
> this (in an inter-operable way?) would be adjusting the
> "pointer-events" property  to "visible".
I don't think this will work in Batik and I don't think it would
be an interoperable. My above suggestion should work for any