[Webkit-unassigned] [Bug 8130] New: More precise event.offsetX and event.offsetY implementation

[bugzilla-daemon at opendarwin.org]

http://bugzilla.opendarwin.org/show_bug.cgi?id=8130

           Summary: More precise event.offsetX and event.offsetY
                    implementation
           Product: WebKit
           Version: 416.x
          Platform: Macintosh
               URL: http://www.gtalbot.org/BrowserBugsSection/Opera9Bugs/Ope
                    ra7BugOffsetXY.html
        OS/Version: Mac OS X 10.4
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: JavaScript
        AssignedTo: webkit-unassigned at opendarwin.org
        ReportedBy: browserbugs at gtalbot.org


Since event.offsetX and event.offsetY are part of the Internet Explorer event
model (and not part of the DOM 2 Event interface), then I strongly propose to
implement these 2 event properties as they work in MSIE 6 and MSIE 7 beta 2
build 5335.5.

Now, empirically speaking, we can see that IE 6 and IE 7 beta 2 implementation
of event.offsetX/event.offsetY return the x/y mouse coordinates within the
element, *_including the padding_* but excluding borders. 

event.offsetX/event.offsetY, as implemented in IE 6+, return the mouse
coordinates within the target element *_according to the padding box_*, not
according to the content box.

Steps to reproduce: 
1- Load provided URL
2- Click exactly inside the green square exactly in the middle of the grid.

Expected results: 
event.offsetX should be 200 (not 50), event.offsetY should be 200 (not 50).

Actual results in Safari 2.02 (416.13):
event.offsetX is 50, event.offsetY is 50.

Fixing this bug helps DHTML application to work reliably across browsers.


-- 
Configure bugmail: http://bugzilla.opendarwin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.