Re-enable inline autocomplete once its blockers are fixed

VERIFIED FIXED in Firefox 13

Status

()

Firefox
Location Bar
VERIFIED FIXED
5 years ago
a year ago

People

(Reporter: mak, Assigned: mak)

Tracking

Trunk
Firefox 13
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(firefox13-)

Details

(Assignee)

Description

5 years ago
Filing this just to track the re-enable.
(Assignee)

Comment 1

5 years ago
https://hg.mozilla.org/integration/mozilla-inbound/rev/1ffea9163a9d
Assignee: nobody → mak77
Target Milestone: --- → Firefox 13
(Assignee)

Comment 2

5 years ago
https://hg.mozilla.org/mozilla-central/rev/1ffea9163a9d
Status: NEW → RESOLVED
Last Resolved: 5 years ago
tracking-firefox13: --- → ?
Resolution: --- → FIXED

Comment 3

5 years ago
What is the about:config pref to disable this thing?

browser.urlbar.autocomplete.enabled set to false does nothing.  Is this a bug?  I need this disabled, because I use an extension called URL Alias, and this autocomplete is seriously screwing up my workflow.

Thanks

Comment 4

5 years ago
I see that the pref now used is browser.urlbar.autoFill; however, "browser.urlbar.autocomplete.enabled" still exists as a valid default pref (which apparently does nothing).  I guess someone should delete that.
(Assignee)

Comment 5

5 years ago
(In reply to IU from comment #4)
> I see that the pref now used is browser.urlbar.autoFill; however,
> "browser.urlbar.autocomplete.enabled" still exists as a valid default pref
> (which apparently does nothing).  I guess someone should delete that.

browser.urlbar.autocomplete.enabled controls the autocomplete popup results.
browser.urlbar.autoFill controls the urlbar autofill results.

Comment 6

5 years ago
Just to confirm, autoFill is true on Aurora 13 right now. You just can't update to it on the aurora branch yet per bug 735421.
Status: RESOLVED → VERIFIED

Updated

5 years ago
tracking-firefox13: ? → -
Depends on: 740076
(Assignee)

Comment 7

5 years ago
Gavin, what does the dependency mean? should we consider bug 740076 a blocker?
No, I just wanted to indicate that that bug was a regression from re-enabling inline autocomplete (and thus should probably be fixed for 13, where this landed).

Comment 9

a year ago
If this is the change that makes the awesomebar show the top-level site above the most relevant page: how can I turn this *off*, and should it be off by default?  When I type 'y', the top entry used to be https://www.youtube.com/feed/subscriptions , which I have bookmarked and visit regularly (as I find it far more useful than the front page).  However, now I see "Visit youtube.com/" as the top entry, and have to hit down once to get to the relevant bookmark for the subscriptions page.

I don't even have youtube.com in my history; I've repeatedly deleted it from there.  Despite that, I occasionally find myself visiting the front page by accident because I didn't hit "down" before "enter".

I understand that in some cases it may make sense to prioritize the top-level site instead of one of many pages visited from that site.  But when there's a page that's far more relevant (and even bookmarked), and the front page has little to no frecency, there should be some threshold where the top-level site stays buried where it belongs.
(Assignee)

Comment 10

a year ago
(In reply to Josh Triplett from comment #9)
> If this is the change that makes the awesomebar show the top-level site
> above the most relevant page: how can I turn this *off*, and should it be
> off by default?  When I type 'y', the top entry used to be
> https://www.youtube.com/feed/subscriptions , which I have bookmarked and
> visit regularly (as I find it far more useful than the front page). 
> However, now I see "Visit youtube.com/" as the top entry, and have to hit
> down once to get to the relevant bookmark for the subscriptions page.

You can disable browser.urlbar.autoFill, but you'll still not get the behavior you are expecting, for that you may need a userChrome css hack to hide the first autocomplete row. I know it has been posted multiple times on the firefox reddit group.

> I don't even have youtube.com in my history; I've repeatedly deleted it from
> there.  Despite that, I occasionally find myself visiting the front page by
> accident because I didn't hit "down" before "enter".

Regardless, even hiding the first row, you'll have to down before enter. It has been like that from a long time. Maybe you were using an add'on like EnterSelects?

> I understand that in some cases it may make sense to prioritize the
> top-level site instead of one of many pages visited from that site.  But
> when there's a page that's far more relevant (and even bookmarked), and the
> front page has little to no frecency, there should be some threshold where
> the top-level site stays buried where it belongs.

Thank you for your feedback, we are indeed already evaluating alternatives in bug 1239708.
You need to log in before you can comment on or make changes to this bug.