commit c1ec13c094cbef4d9f36e22677f9f6e3844fc3bf
author gwt.team.knorton <gwt.team.knorton@8db76d5a-ed1c-0410-87a9-c151d255dfc7> Wed May 02 17:41:33 2007 +0000
committer gwt.team.knorton <gwt.team.knorton@8db76d5a-ed1c-0410-87a9-c151d255dfc7> Wed May 02 17:41:33 2007 +0000
tree 76a01ca5b285f558957256054020de71b074aa64
parent 45919c25dd9f1e41b4484020088aa79f3de3d23c

Fixes Issue #286.
Mouse event coordinates have been unreliable under various scrolling
scenarios. This patch addresses the various issues that were
responsible. First, it fixes a bug with getAbsoluteTop/Left for
DOMImplStandard and DOMImplSafari where scrolling was not full
accounted for due to a walk of the offsetParent not the parentNode.
Secondly, it adds the appropriate scroll offset for body and the
current element for MouseListenerCollection and MouseWheelCollection.
Thirdly, it changes DOM.eventGetClientX/Y to rely on pageX/Y for
DOMImplSafari since Safari2 returns the wrong value for clientX/Y
(This also makes the solution work on hosted mode's WebKit and WebKit
tip where the clientX/Y bug has been fixed).

Patch by: knorton, fredsa
Review by: jgw, ecc



git-svn-id: https://google-web-toolkit.googlecode.com/svn/trunk@1005 8db76d5a-ed1c-0410-87a9-c151d255dfc7