Closed Bug 1060340 Opened 5 years ago Closed Last year

Double-clicking the location bar dropdown arrow changes awesomebar behavior with non-default maxRichResults

Categories

(Firefox :: Address Bar, defect, P5)

All
Windows 7
defect

Tracking

()

RESOLVED INACTIVE

People

(Reporter: ge3k0s, Unassigned)

References

Details

(Whiteboard: [see bug 1195054 comment 1][fxsearch])

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:34.0) Gecko/20100101 Firefox/34.0 (Beta/Release)
Build ID: 20140828030205

Steps to reproduce:

1. Click the dropdown arrow in the location bar.
2. Awesomebar appears
3. Close it
4. Type anything in the location bar



Actual results:

12 results are displayed without scrollbar (if there are enough history entries).


Expected results:

6 results are displayed with 6 more beneath using the scrollbar.
Component: Untriaged → Location Bar
Hardware: x86_64 → All
I can't reproduce this. Have you tried on a clean profile (admittedly, it'll take a little bit of work to get some history for 12 results - maybe just do a bunch of searches and then type in the name of the search provider) ?
Flags: needinfo?(ge3k0s)
(In reply to :Gijs Kruitbosch from comment #1)
> I can't reproduce this. Have you tried on a clean profile (admittedly, it'll
> take a little bit of work to get some history for 12 results - maybe just do
> a bunch of searches and then type in the name of the search provider) ?

It may be related to bookmarks since it seems that entries are mainly bookmarks. I will try on a new profile when I have the time.
Flags: needinfo?(ge3k0s)
Ah I found a mistake in my STR. You have to double click the dropdown arrow.
In fact this is maybe by design and I find this useful.
(In reply to Guillaume C. [:ge3k0s] from comment #3)
> Ah I found a mistake in my STR. You have to double click the dropdown arrow.

Can't reproduce on OS X, but I can reproduce on Windows...

I doubt this is by design (I suspect not, per comments in the other bug...), but Dão would know for sure.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: needinfo?(dao)
Summary: Clicking the location bar dropdown arrow changes awesomebar behavior → Double-clicking the location bar dropdown arrow changes awesomebar behavior
(In reply to :Gijs Kruitbosch from comment #5)
> (In reply to Guillaume C. [:ge3k0s] from comment #3)
> > Ah I found a mistake in my STR. You have to double click the dropdown arrow.
> 
> Can't reproduce on OS X, but I can reproduce on Windows...
> 
> I doubt this is by design (I suspect not, per comments in the other bug...),
> but Dão would know for sure.

I've never heard of this, don't think it's intentional. I can't reproduce this on Linux either.
Flags: needinfo?(dao)
not intentional at all.
This is not reproducible anymore. Maybe - because dropmarker was broken and doesn't hide awesomebar.

However, "12 results"-thing hasn't disappeared, and I've found another STR that works with new versions (because G-d knows, I was very angry having this issue for ~3 years. And I still experience it).
See Also: → 1195054
See Also: → 1199875
Yes this isn't reproducible anymore.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WORKSFORME
My bad I was able to reproduce right now...
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
(In reply to Guillaume C. [:ge3k0s] from comment #10)
> My bad I was able to reproduce right now...
Me too. See also bug 1195054 comment 1 - the reason why nothing was done over these years.
Whiteboard: see bug 1195054 comment 1
Depends on: 1195054
I think we can close this now that all results are shown by default.
Status: REOPENED → RESOLVED
Closed: 4 years ago4 years ago
Resolution: --- → WORKSFORME
I still have this bug with "browser.urlbar.maxRichResults" set to "20"
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
(In reply to arni2033 from comment #13)
> I still have this bug with "browser.urlbar.maxRichResults" set to "20"

That really sounds like an edge case not really worth fixing to me. Marco what do you think of it ?
Flags: needinfo?(mak77)
Blocks: fx-qx
No longer blocks: fx-qx
(In reply to Guillaume C. [:ge3k0s] from comment #14)
> That really sounds like an edge case not really worth fixing to me.
So that sounds like your bug is gone and now you don't care about the others. Nice attitude.
(In reply to arni2033 from comment #15)
> (In reply to Guillaume C. [:ge3k0s] from comment #14)
> > That really sounds like an edge case not really worth fixing to me.
> So that sounds like your bug is gone and now you don't care about the
> others. Nice attitude.

If you mess with prefs in about:config it's likely to break things. Personally I think it would be better to completely get rid of the arrow like UX was planning a while ago (it lead to the current beahviour of showing it only on hover).
(In reply to Guillaume C. [:ge3k0s] from comment #16)
> If you mess with prefs in about:config it's likely to break things.
It's not only "me messing with prefs" - extensions use them when they can, so it's more wide-spreaded
One thing I know for sure: if that pref didn't exist, there'd be no bug. But there it is. The pref.

> Personally I think it would be better to completely get rid of the arrow like UX was planning
> a while ago (it lead to the current beahviour of showing it only on hover).
I can reproduce this bug without dropmarker at all; this bug was just.. convenient. It's already filed

But since you mentioned dropmarker:
I try not to use it and don't rely on it anyhow, sometimes I just encounter this bug and others involving dropmarker. I'm OK with things I don't use as long as they don't cause bugs. But it's obvious that current UX is strictly worse than both removing the arrow and keeping it visible (causes blinking and bugs below). It just shows that Mozilla devs don't have strong opinion on that.
> bug 1220486, bug 1238637, bug 1244420
we can morph the bug slightly.
clearly the fact it doesn't happen with default settings reduces its priority to something good for the community, but it's still a valid bug that lies somewhere in the code.
Flags: needinfo?(mak77)
Priority: -- → P5
Summary: Double-clicking the location bar dropdown arrow changes awesomebar behavior → Double-clicking the location bar dropdown arrow changes awesomebar behavior with non-default maxRichResults
Whiteboard: see bug 1195054 comment 1 → [see bug 1195054 comment 1][fxsearch]
Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.
Status: REOPENED → RESOLVED
Closed: 4 years agoLast year
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.