212081 - Location Bar Overflow-Tooltip is off by 3 addresses

Status: RESOLVED FIXED

(SeaMonkey :: Location Bar, defect)

Description

[cooperg]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624

When mousing over a very long URL in the Location Bar's history-dropdown the 
URL it displays is off by 3 addresses. 

Reproducible: Always

Steps to Reproduce:
1. In the URL bar type "google". 

(Assuming you use Google a lot,) Mozilla will automatically bring up a snazzy
dropdown of all your old searches. Unfortunately not much shows up regarding
what you actually searched for (~20 chars) so you have to mouse over the URL to
see what the rest of your search was. 

2. Mouse over the URLs in the list. 

Notice that the first 3 URLs have no tooltip entry. Starting with the 4th URL
the tooltips appear, but the indexes are off, so the 4th entry gets the 1st
entry's tooltip!

Comment 1

[Son Le]

Confirmed

Comment 2

[Son Le]

Attachment: patch v0

fix and a bit of a cleanup (remove unused view)

Comment 3

[[e-mail]]

Comment on attachment 181967 [details] [diff] [review]
patch v0

bz, this is basically the same issue as the autocomplete mouseover bug, with
the difference that this code is also used for non-popup trees. Do you want
this hack or do you want to fix popup coordinates?

>+  if (!mSourceNode)
>+    return;
>+
>+  nsCOMPtr<nsIBoxObject> bx;
>+  nsCOMPtr<nsIDOMXULElement> xulEl(do_QueryInterface(mSourceNode));
>+  xulEl->GetBoxObject(getter_AddRefs(bx));
You don't actually have to jump though these hoops, because
GetSourceTreeBoxObject already did the legwork for you.

>+
>   nsCOMPtr<nsITreeBoxObject> obx;
>   GetSourceTreeBoxObject(getter_AddRefs(obx));
>-  if (obx) {
      nsCOMPtr<nsIBoxObject> bx(do_QueryInterface(obx)); should suffice.

Comment 4

[Boris Zbarsky [:bzbarsky]]

I think in the short term we need the hack, since fixing popup coordinates is an
alpha-type change...

That said, the patch looks wrong to me, since the x and y on boxObject aren't
exactly client coords.  Shouldn't the right thing be to just take the event
screen coords and subtract the screen coords of the boxObject for the
documentElement of the document the target tree is in?

Especially so because it's not clear to me whether bx and obx are even required
to be in the same document.

Comment 5

[Boris Zbarsky [:bzbarsky]]

Comment on attachment 181967 [details] [diff] [review]
patch v0

r-.  To see why, just put borders on some things (say a 100px border on the
root element of the document the tree is in) and watch the x/y boxObject coords
screw you over.

Comment 6

[[e-mail]]

Ah, so the fix for revision 1.114 of autocomplete.xml actually works generically!

Comment 7

[Boris Zbarsky [:bzbarsky]]

Yes, it does.  Part of the reason I went with it... ;)

Comment 8

[Son Le]

Attachment: patch v1

changed to subtracting the screen coords of the boxObject for the
documentElement

Comment 9

[Boris Zbarsky [:bzbarsky]]

Comment on attachment 182313 [details] [diff] [review]
patch v1

Let me know if you need this checked in, ok?

Comment 10

[[e-mail]]

Comment on attachment 182313 [details] [diff] [review]
patch v1

This works, except there appears to be an include missing:
@@ 50,6 +50,7 @@
 #include "nsIServiceManager.h"
 #ifdef MOZ_XUL
 #include "nsITreeView.h"
+#include "nsIDOMNSDocument.h"
 #endif
 #include "nsGUIEvent.h"
 #include "nsIPrivateDOMEvent.h"

Comment 11

[Son Le]

Attachment: patch v1.1

Added missing include (it was in the header file which I forgot to include).

bzbarsky, if you could check it in that would be great!

Comment 12

[Son Le]

Comment on attachment 182313 [details] [diff] [review]
patch v1

make XUL tooltips work

Comment 13

[chris hofmann]

Comment on attachment 182313 [details] [diff] [review]
patch v1

a=chofmann

Comment 14

[Boris Zbarsky [:bzbarsky]]

Patch checked in for 1.8b2.  Thanks for fixing this!

Comment 15

[Majken Connor [:Kensie]]

*** Bug 269522 has been marked as a duplicate of this bug. ***