Closed
Bug 91325
Opened 23 years ago
Closed 14 years ago
Autocomplete dropdown goes blank on mouseover
Categories
(Core :: XUL, defect, P3)
Tracking
()
RESOLVED
INVALID
Future
People
(Reporter: srilatha, Unassigned)
References
Details
(Keywords: regression)
Attachments
(1 file)
1002 bytes,
patch
|
Details | Diff | Splinter Review |
When I move the mouse over the autocomplete dropdown box it goes blank if there is only one item. This happens with the location bar dropdown and also in the compose window. If there are more than one item in the dropdown box, the items scroll up and there is an extra empty item at the bottom of the list. But if I try to scroll up and down with the arrow keys I can see the items in there. This happens with Classic skin but not with modern skin This happens on yesterday's trunk build but not on the branch. I've seen this happen in my debug build from 7/11 too.
Reporter | ||
Comment 1•23 years ago
|
||
I am not sure I set the right component. Adding regression keyword. dmose hasn't seen this on Linux. May be it is windows specific bug
Keywords: regression
Reporter | ||
Comment 2•23 years ago
|
||
updated summary
Summary: Aucomplete dropdown goes blank on mouseover → Autocomplete dropdown goes blank on mouseover
Reporter | ||
Comment 4•23 years ago
|
||
I see it on linux too.
Comment 5•23 years ago
|
||
I'm seeing this in 2001071903 on win2k as well. Additionally, if I scroll up/down the text in the pulldown changes to a pale green color and I can't click and drag to scroll any more. In composer, most of the list dissapears on mouseover, and there's no scrollbar either.
Updated•23 years ago
|
Status: NEW → ASSIGNED
Comment 6•23 years ago
|
||
Updated•23 years ago
|
Target Milestone: --- → mozilla0.9.3
Comment 7•23 years ago
|
||
r=jag. This won't fix the issue I (and probably others) are seeing in the modern skin on linux because of some low-level problem with our font metrics.
Updated•23 years ago
|
Target Milestone: mozilla0.9.3 → mozilla0.9.4
Reporter | ||
Updated•23 years ago
|
Keywords: nsenterprise
Updated•23 years ago
|
OS: Windows NT → Linux
Target Milestone: mozilla0.9.4 → ---
Comment 8•23 years ago
|
||
May God have mercy on us all. The 212 bug spam-o-rama is Now!
QA Contact: aegis → jrgm
Updated•23 years ago
|
Priority: -- → P3
Target Milestone: --- → mozilla1.0
Comment 10•23 years ago
|
||
marking nsenterprise-; will be reevaluated for nsenterprise in future release.
Keywords: nsenterprise-
Comment 11•23 years ago
|
||
jag tells me that this depends on some linux font issues getting fixed, and since I have no idea when that will get fixed, marking Future
Target Milestone: mozilla1.0 → Future
Comment 12•23 years ago
|
||
I thought those font issues had been fixed already, but I could be mixing things up. The problem is less now, it used to be so that if I had two items in the dropdown, they would both go away, now only one goes away.
Comment 13•21 years ago
|
||
I see now that bug on Win2000 as well ( build 2004010608) with extend that menu goes white also when pressing down arrow when pressing Enter or clicking on empty menu Mozilla tries to load uncomplete URL instead of taking it from the menu.
Updated•15 years ago
|
Assignee: hewitt → nobody
Status: ASSIGNED → NEW
QA Contact: jrgmorrison → xptoolkit.widgets
Comment 14•14 years ago
|
||
OP, could you confirm if this bug is still present in current TB? I'm using TB 2.0.0.24 in Ubuntu 9.10, but I can't get such problem. Anyway, in TB2, there's no more classic or modern skin, just default theme. So, maybe the bug is solved already?
Comment 15•14 years ago
|
||
As the original reporter didn't reply and on the other hand skin is no longer present in current version, this bug will be closed as invalid.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → INVALID
Resolution: INVALID → WORKSFORME
Comment 16•14 years ago
|
||
I don't understand why WORKSFORME should be chosen. If you use older versions of TB, you could see that the reported bug is still there, so it never *works*. But at current version, this bug no longer makes any sense. That's why I chose INVALID (for current version).
Resolution: WORKSFORME → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•