Internet Explorer now works the same as Firefox. That is, with real zoom, absolute positions do not change even though the widget appears further from the left or top. I was going to put that info in the review request, but I didn't want to confuse anyone.
> Also, can you check what happens when you use your patched > getAbsoluteLeft + getAbsoluteTop to calculate the distance between two > widgets? For example > Do we really need to test this? I verified that getAbsoluteLeft() returns the correct value now and is consistent between FF and IE, and I verified it against the MenuBar and SuggestBox. The fact that SuggestBoxPopup opens directly below the TextBox and MenuBarPopup opens directly below the MenuBar implicitly verified that getAbsoluteTop() + getOffsetHeight() already works. offsetHeight/Width didn't seem to be affected by this issue at all. Thanks, John LaBanca [EMAIL PROTECTED] On Mon, Dec 8, 2008 at 6:29 PM, <[EMAIL PROTECTED]> wrote: > Have you checked to see what values getAbsoluteLeft/Top give in your > demo with Firefox3 and Opera? It seems like we want all the real zooming > browsers to handle this the same way. > > Also, can you check what happens when you use your patched > getAbsoluteLeft + getAbsoluteTop to calculate the distance between two > widgets? For example > > Widget a (absolutely positioned at (100,100) 50 px tall. > > Widget b flows naturally after widget a. There are no styles on any > widget to confuse this poor example. > > Widget c's height is calculated to be getAbsoluteTop(a) - > getAbsoluteTop(b) > > is Widget c's height the same as widget a's? > > > > http://gwt-code-reviews.appspot.com/807 > --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
