Closed Bug 56647 Opened 26 years ago Closed 24 years ago

Autocomplete menu has URL bar tooltip

Categories

(SeaMonkey :: Location Bar, defect, P3)

defect

Tracking

(Not tracked)

RESOLVED WORKSFORME
mozilla1.0

People

(Reporter: bugzilla, Assigned: hewitt)

References

Details

(Keywords: regression)

Attachments

(1 file, 1 obsolete file)

If you hover over an item in the autocomplete menu, it has the URL bar tooltip, because the menu doesn't specify a tooltip and therefore it derives from the parent (the textfield). I have a fix for this, but it's in the XML, which isn't good for skinnability reasons. Ducarroz, please see my question in bug 56646 about styling this menu in a .css file.
JF...?
Status: NEW → ASSIGNED
Component: Browser-General → XP Apps: GUI Features
QA Contact: doronr → sairuh
Target Milestone: --- → mozilla1.0
this problem doesn't occurs on Mac but does occur in Linux! Ross, I don't really have an answer for your question, see bug 56646
we need also to add a rule to remove the max width use actually by the menu item!
OS: Windows 98 → All
Priority: P3 → P4
Hardware: PC → All
Not sure what to do with this one, so handing over to JF for now...
Assignee: blakeross → ducarroz
Status: ASSIGNED → NEW
Priority: P4 → --
Target Milestone: mozilla1.0 → ---
Bug 63576 says there shouldn't be a tooltip for short urls in the dropdown, and that for long urls the tooltip should be the entire url.
QA Contact: sairuh → tpreston
Black Ross, what's your fix for the tooltip matter? I have a fix for the menu width problem but I cannot figure out how to remove those anoying tooltip...
*** Bug 63576 has been marked as a duplicate of this bug. ***
Pinkerton, For some reason the menu "inherrite" the tooltip from the textfield. But if I setup my own tooltip for the menuitem, this one still show the wrong one. Any idea how I can tell the popup menu to use it's own tooltip or no tooltip at all?
The menu is supposed to inherit the tooltip from its parent (the textfield) unless it's overridden. I swear I had a fix for this awhile back, but it doesn't seem to be working anymore. And no, I don't know what I as talking about when I said styling this in css in my original report. Maybe I meant dtd.
Netscape nav triage team: as per Alec Flett's pre-triage recommendation, this bug is nsbeta1-.
Keywords: nsbeta1-
pardon da spam...
Component: XP Apps: GUI Features → History: URLBar
taking, marking dependency. This is fixed by the patch in 43189.
Assignee: ducarroz → hewitt
Depends on: 43189
Status: NEW → ASSIGNED
This isn't fixed by the patch in 43189 as far as I can tell from the experimental build.
Using both modern/classic, this seems to be fixed.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
The bug is that hovering over an autocomplete menuitem shows a tooltip, and it's still there for me in a new nightly. Meet me outside the parking lot of b21 at night if you wanna challenge that ;)
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
this has gotten much much worse with the new AC widget. now hovering over anything in that widget, even the scrollbar, shows the url bar tooltip. it makes the AC widget pretty darn hard to use with the mouse.
Severity: normal → major
Yuck. I wish I could reproduce this, but my tree builds, and the sweetlou build I downloaded today do not demonstrate the problem.
Status: REOPENED → ASSIGNED
i'm using a sweetlou build on mac from 5/1
Themes Triage Team marking nsbeta1+
Target Milestone: --- → mozilla0.9.1
This is driving me INSANE. I'm trying to solve this by setting "inputtooltip" and "inputtooltiptext" on the autocomplete <textbox/>, then inheriting those attributes to the anonymous <html:input/> and/or it's <xul:box/> parent as "tooltip" and "tooltiptext". But the gosh darn tooltip won't show. I've tried setting those attributes on many different combinations of anon. content, and the only success I've had is setting them on a popup or a button with allowevents="true". What is this bullocks?! Is this coming down to a bug with the tooltip system or what?
not gonna get done in time -> 0.9.2
Keywords: nsbeta1+
Target Milestone: mozilla0.9.1 → mozilla0.9.2
themes triage: Not an rtm stopper - moving to 0.9.3.
Target Milestone: mozilla0.9.2 → mozilla0.9.3
Target Milestone: mozilla0.9.3 → mozilla0.9.4
Severity: major → normal
Target Milestone: mozilla0.9.4 → ---
Priority: -- → P3
Target Milestone: --- → mozilla0.9.7
I'll get to this during the next milestone when I re-write the way tooltips work.
Target Milestone: mozilla0.9.7 → mozilla0.9.8
*** Bug 112610 has been marked as a duplicate of this bug. ***
Target Milestone: mozilla0.9.8 → mozilla0.9.9
Target Milestone: mozilla0.9.9 → mozilla1.0
I can reproduce this 100%. The tooltip text is the same as the last tooltip shown. For instance, if I hoover over personal toolbar link to get a tooltip and then expand URL list, the tooltip over URL list is the same. Win2K. Moz 0.9.8 (Build 2002020406)
Attachment #34628 - Attachment is obsolete: true
So hewitt's patch doesn't work because of two problems: * We don't register tooltip listeners if html elements in xul docs request tooltips. * The target content for the mousemove event when you hover over the urlbar isn't the containing box, but html:input (this isn't really a problem but a reality) So although we did register a tooltip listener on the containing box with hewitt's patch, when we looked for tooltiptext on the html:input when mousing over, we found none. This loser patch gets us to register the tooltip listener on the containing box via the tooltiptext attr, and then ensures that we find the tooltiptext by placing it on the html:input. This is not a general fix but a fix for this specific, highly annoying bug. I presume a real fix would search a target content's children for tooltiptext if not found on the target content.
*** Bug 114978 has been marked as a duplicate of this bug. ***
This bug was really annoying, so I checked in the attached 'fix'. I guess I'll leave this bug open to deal with the tooltip issue in general.
Keywords: nsbeta1
nsbeta1- per Nav triage team, resolving as wfm, please open a new bug for general case.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago → 24 years ago
Keywords: nsbeta1 → nsbeta1-
Resolution: --- → WORKSFORME
Still a problem for the location bar *context menu* (bug 133788).
Product: Core → SeaMonkey
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: