[Webkit-unassigned] [Bug 44083] New: SVGLocatable.getScreenCTM uses page{X, Y} rather than client{X, Y}

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=44083

           Summary: SVGLocatable.getScreenCTM uses page{X,Y} rather than
                    client{X,Y}
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: PC
               URL: http://graphics.stanford.edu/~mbostock/getScreenCTM.ht
                    ml
        OS/Version: Mac OS X 10.5
            Status: UNCONFIRMED
          Severity: Normal
          Priority: P2
         Component: SVG
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: mbostock at cs.stanford.edu
                CC: zimmermann at kde.org, mbostock at cs.stanford.edu


Created an attachment (id=64541)
 --> (https://bugs.webkit.org/attachment.cgi?id=64541)
Test case.

Per SVG Tiny 1.2, Section A.8.11 SVGLocatable:

"""
getScreenCTM

Returns the transformation matrix from current user units to the initial viewport coordinate system. The clientX and clientY coordinates of a MouseEvent are in the initial viewport coordinate system. Note that null is returned if this element is not hooked into the document tree. This method would have been more aptly named as getClientCTM, but the name getScreenCTM is kept for historical reasons.
"""

In WebKit (and Safari, Chrome), the matrix returned by getScreenCTM considers the scrollTop and scrollLeft. Therefore, it is as if pageX and pageY were used instead of clientX and clientY, as described by the spec. Firefox and Opera exhibit the correct behavior, consistent with clientX and clientY.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.