W3C home > Mailing lists > Public > public-svg-wg@w3.org > October to December 2008

Clipping and pointer-events erratum

From: Cameron McCormack <cam@mcc.id.au>
Date: Wed, 26 Nov 2008 10:23:26 +1100
To: public-svg-wg@w3.org
Message-ID: <20081125232326.GB20757@arc.mcc.id.au>

Batik would be a beneficiary of getting
http://www.w3.org/Graphics/SVG/Group/repository/errata/errata.xml#clippath-pointer-events
done.


----- Forwarded message from thomas.deweese@kodak.com -----

From: thomas.deweese@kodak.com
Date: Tue, 25 Nov 2008 06:48:46 -0500
To: batik-users@xmlgraphics.apache.org
Cc: batik-users@xmlgraphics.apache.org
Subject: Re: Likely Batik bug with SVG scrollbars

Hi John,

"John C. Turnbull" <ozemale@ozemail.com.au> wrote on 11/25/2008 02:27:51 
AM:

> [..] open the SVG in Batik you will find that if 
> you drag the lower image up as far as it can go and then try to use 
> the top horizontal scroll bar, the lower image will be scrolled 
> instead.  It seems that Batik thinks the lower image has moved over 
> the top of the upper one which is not the case.

   Actually it has, it's just that it's drawing was clipped. 
Last time I checked it was unclear if SVG events should respect
clipping or not (there are arguments on both sides).

   Anyway take a look at:
        https://issues.apache.org/bugzilla/show_bug.cgi?id=46289

> Can anyone see why this buggy behaviour is happening?  Can it be 
> fixed?  Getting SVG scrollbars to work with Batik is critical to my 
> current project so I really need to resolve this.

   I'm not sure it's really buggy behavior.

----- End forwarded message -----

-- 
Cameron McCormack ≝ http://mcc.id.au/
Received on Tuesday, 25 November 2008 23:24:04 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 25 November 2008 23:24:09 GMT