Bug 46289 - Pointer Events Don't respect clipping.
Pointer Events Don't respect clipping.
Status: NEW
Product: Batik - Now in Jira
Classification: Unclassified
Component: (RFE) Request For Extension
PC Windows XP
: P2 normal
: ---
Assigned To: Batik Developer's Mailing list
Depends on:
  Show dependency tree
Reported: 2008-11-25 03:46 UTC by Thomas Deweese
Modified: 2010-01-31 10:10 UTC (History)
0 users

Makes event handling respect clipping. (3.68 KB, patch)
2008-11-25 03:46 UTC, Thomas Deweese
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Deweese 2008-11-25 03:46:25 UTC
Created attachment 22936 [details]
Makes event handling respect clipping.

I'm not sure what the current status on this issue is.
Neither SVG 1.1 or SVG 1.2 Tiny says anything about clipping
with respect to when 'relevant graphical content is under the pointer'.

Anyway I've created a patch that makes Batik's event handling
sensitive to clipping.
Comment 1 Helder Magalhães 2008-12-04 12:35:09 UTC
Well, I took the freedom of starting a thread [1] in the SVG-WG, using this issue as inspiration, which resulted in a clarification [2] by the SVG-WG.

As far as I was able to confirm, the patch doesn't seem to be enough to make Batik respect the whole proposed changes, but IMO it would be reasonable to land it whenever possible and file a separate issue for any remaining issue (possibly treat "pointer-events" set to "all" and maybe more - if this isn't already being done by the framework, of course).

Hope this helps,

 Helder Magalhães

[1] http://lists.w3.org/Archives/Public/www-svg/2008Nov/0064.html
[2] http://lists.w3.org/Archives/Public/www-svg/2008Dec/0007.html
Comment 2 Helder Magalhães 2010-01-31 07:36:51 UTC
Update: the SVG WG has pronounced [1] regarding this, in the scope of SVG 1.1 SE. 

There's an important detail in the reply, which is: «in the interest of publishing the SVG 1.1 2nd edition spec, we ask folks to respond within 2 weeks.» [1], which is in about a week as of this writing.

According to my understanding of the currently proposed text for SVG 1.1 SE [1], this patch would be landed. I'm not really into the details/implications of that, but felt like it was a good idea to ping on this (so it can be further discussed, if needed). :-)

[1] http://lists.w3.org/Archives/Public/www-svg/2010Jan/0086.html
Comment 3 Helder Magalhães 2010-01-31 10:10:40 UTC
(In reply to comment #2)
> According to my understanding of the currently proposed text for SVG 1.1 SE,
> this patch would be landed.

The applicable errata test cases seem to be:

1. interact-pointer-02-t:
 * Squiggle currently fails;
 * With this patch applied, it fails as well;
 * There seems to be a weird (possibly unrelated) behavior after passing the mouse over the (red) rectangle: a "null" exception is thrown. It happens with both patched and original code.

2. interact-pointer-03-t:
 * Squiggle refuses to render given the broken reference to the clip-path;
 * I'm trying to clarify this with the SVG WG.

Both were grabbed from an implementation report [3].

[1] http://dev.w3.org/SVG/profiles/1.1F2/test/svg/interact-pointer-02-t.svg
[2] http://dev.w3.org/SVG/profiles/1.1F2/test/svg/interact-pointer-03-t.svg
[3] http://dev.w3.org/SVG/profiles/1.1F2/errata/implementation-report.html