DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=36165>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=36165 Summary: getScreenCTM and evt.screenX/Y mismatch Product: Batik Version: 2.0 Platform: PC URL: https://bugzilla.mozilla.org/show_bug.cgi?id=293224 OS/Version: Windows 2000 Status: NEW Severity: major Priority: P2 Component: SVG DOM AssignedTo: [email protected] ReportedBy: [EMAIL PROTECTED] We've had a bug reported on Mozilla's implementation of getScreenCTM, but it seems that Batik's implementation of this method is at fault. On your MouseEvent events the screenX and screenY attributes have values in a coordinate system that has its origin at the top left of the physical screen as expected. However, getScreenCTM returns a matrix to a coordinate system that has its origin at the top left of Batik's *client* area. Unfortunately this seems to be causing people to incorrectly use *client*X/Y with getScreenCTM. Please see the Mozilla bug for testcases and discussion. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
