Closed
Bug 257722
Opened 20 years ago
Closed 17 years ago
No visual feedback when clicking on scrollbarbutton in autocomplete popups (no depressed state)
Categories
(Firefox :: Address Bar, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: martijn.martijn, Assigned: martijn.martijn)
References
Details
(Keywords: polish)
Attachments
(3 files)
1.85 KB,
patch
|
neil
:
review-
|
Details | Diff | Splinter Review |
1.88 KB,
patch
|
neil
:
review+
beltzner
:
approval1.9+
|
Details | Diff | Splinter Review |
2.15 KB,
patch
|
neil
:
review+
|
Details | Diff | Splinter Review |
See for example the url bar. Open the url bar autocomplete popup. Click on the scrollbarbutton (up or down). You won't see that the scrollbarbutton is clicked upon. This is different from a 'normal' scrollbar. I've even seen this bug in Firefox0.7, so if this is a regression, it is some time ago. I don't think this is a simple theme issue. I've played with some css rules for scrollbars. I can get :hover rules to apply for scrollbarbuttons in autocomplete popups, but not :active rules.
Updated•20 years ago
|
Severity: trivial → normal
Comment 1•20 years ago
|
||
this bug is present in Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 also.
Comment 2•18 years ago
|
||
Mass edit: Changing QA to default QA Contact
QA Contact: davidpjames → password.manager
Comment 3•18 years ago
|
||
Mass edit: Setting correct QA for location bar/autocomplete. My bad. I forgot I had once been Autocomplete QA too. Hmm, why can't I just set the QA of bugs to the default QA of the component in a mass edit rather than having to do it manually...?
QA Contact: password.manager → location.bar
Updated•17 years ago
|
Assignee: bugs → nobody
Assignee | ||
Comment 4•17 years ago
|
||
This fixes it for me. I'm wondering why Seamonkey doesn't have this problem, though.
Attachment #289488 -
Flags: review?(neil)
Comment 5•17 years ago
|
||
(In reply to comment #4) >I'm wondering why Seamonkey doesn't have this problem, though. SeaMonkey Modern is OK, but I see it with both Classic and Winstripe themes.
Comment 6•17 years ago
|
||
Comment on attachment 289488 [details] [diff] [review] patch >+ <xul:tree anonid="tree" class="autocomplete-tree plain" hidecolumnpicker="true" flex="1" style="-moz-user-focus: ignore !important;"> This belongs in xul.css (there's a section for autocomplete). >- <content onmousedown="event.preventDefault()"> >+ <content> Please apply the equivalent fix to xpfe's autocompelte.xml for TB/SM.
Attachment #289488 -
Flags: review?(neil) → review-
Assignee | ||
Comment 7•17 years ago
|
||
Attachment #290132 -
Flags: review?(neil)
Assignee | ||
Comment 8•17 years ago
|
||
This one is untested, I don't have a Seamonkey tree yet (sorry). (I though xpfe was going away or something, last time you said I shouldn't bother with xpfe, or something like that).
Attachment #290133 -
Flags: review?(neil)
Comment 9•17 years ago
|
||
Comment on attachment 290133 [details] [diff] [review] seamonkey patch Works fine. FYI this is one of the few pieces of XPFE chrome that SeaMonkey still uses (the other two are download manager and windows hooks).
Attachment #290133 -
Flags: review?(neil) → review+
Comment 10•17 years ago
|
||
Comment on attachment 290132 [details] [diff] [review] firefox patch > .autocomplete-tree { >+ -moz-user-focus: ignore; > -moz-binding: url("chrome://global/content/bindings/autocomplete.xml#autocomplete-tree"); > } Nit: We normally have the -moz-binding in first (compare e.g. radiogroup).
Attachment #290132 -
Flags: review?(neil) → review+
Assignee | ||
Comment 11•17 years ago
|
||
Comment on attachment 290132 [details] [diff] [review] firefox patch Ok, thanks, I'll change the order on check-in.
Attachment #290132 -
Flags: approval1.9?
Assignee | ||
Updated•17 years ago
|
Attachment #290133 -
Flags: approval1.9?
Assignee | ||
Updated•17 years ago
|
Assignee: nobody → martijn.martijn
Comment 12•17 years ago
|
||
Comment on attachment 290133 [details] [diff] [review] seamonkey patch You don't need approval for SeaMonkey-only patches.
Attachment #290133 -
Flags: approval1.9?
Assignee | ||
Comment 13•17 years ago
|
||
Checking in autocomplete.css; /cvsroot/mozilla/xpfe/components/autocomplete/resources/content/autocomplete.css ,v <-- autocomplete.css new revision: 1.12; previous revision: 1.11 done Checking in autocomplete.xml; /cvsroot/mozilla/xpfe/components/autocomplete/resources/content/autocomplete.xml ,v <-- autocomplete.xml new revision: 1.159; previous revision: 1.158 done Seamonkey patch checked in.
Comment 14•17 years ago
|
||
Comment on attachment 290132 [details] [diff] [review] firefox patch a=beltzner on behalf of drivers
Attachment #290132 -
Flags: approval1.9? → approval1.9+
Assignee | ||
Comment 15•17 years ago
|
||
Checking in xul.css; /cvsroot/mozilla/toolkit/content/xul.css,v <-- xul.css new revision: 1.111; previous revision: 1.110 done Checking in widgets/autocomplete.xml; /cvsroot/mozilla/toolkit/content/widgets/autocomplete.xml,v <-- autocomplete.x ml new revision: 1.91; previous revision: 1.90 done Checked into Firefox.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Comment 16•17 years ago
|
||
It is very nice that this is fixed! But this was not the only place in the UI which had this problem. See for example the "More Actions" drop-down in the new version of Gmail. There is still no depressed state for the scrollbar or scroll arrows. Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b2pre) Gecko/2007112805 Minefield/3.0b2pre ID:2007112805
Assignee | ||
Comment 17•17 years ago
|
||
The drop-down in the new version of Gmail is not a drop-down in the sense of a select drop down. I guess Gmail is using event.preventDefault() in some way on mousedown, so this is not a Firefox problem, but more a problem with the site.
Assignee | ||
Updated•17 years ago
|
Comment 18•7 years ago
|
||
Pushed by frgrahl@gmx.net: https://hg.mozilla.org/comm-central/rev/9d0dcc06751f No visual feedback when clicking on scrollbarbutton in autocomplete popups (no depressed state), r=neil, SeaMonkey-only
You need to log in
before you can comment on or make changes to this bug.
Description
•