We will be doing maintenance work on Vivaldi Translate on the 11th of May starting at 03:00 (UTC) (see the time in your time zone).
Some downtime and service disruptions may be experienced.
Thanks in advance for your patience.
Solved Address bar auto-complete has been ruined
-
Personally, I think what's happening is the first item that should be appearing beneath the address bar as a suggestion is now autocompleting what you've typed in. If this was a bug, please fix it; if this was intentional, please reconsider it. We hate it.
-
@5eagull
Hi, you hate it I haven't even noticed it yet.
You have reported a bug to the tracker, if you like I can add it to my watch list and get back to you if anything happen.Cheers, mib
-
What happened? The autocomplete is now SUPER AGRESSIVE.
I originally had it set up so that auto-complete OPTIONS were available to select, but now I can't even type in the URL bar without it completing stuff, which 99% of the time is not what I want.
Is there an option to turn this off? It's really, really, dumb.
-
Can't edit, above post RESOLVED: seems my settings were changed back to
address bar / auto-complete ONwith latest update. I stupidly posted before checking my settings. -
@AshSimmonds
Hi and no, it is stupid to change such settings with an update.
May this solve also @5eagull problems.Cheers, mib
-
Nope. I always had it on and it always stayed in its box until now.
-
"address bar / auto-complete ON" turning that off is not a solution. I'd like it to work like it used to and turning auto-complete off does not do that.
-
@Shadess
Hi, can you test this in Chrome or other Chromium based browser?
I don´t use the address bar but it seams Chrome does the same, maybe a Chromium 106 "Feature"?Cheers, mib
-
@mib2berlin I don't use chrome enough to say if it's changed with the latest versions or not, but tried it now and the auto-complete on chrome isn't as aggressive as it is on the current vivaldi at least.
-
Confirmed Chrome stable and dev do not work like this so this is strictly a Vivaldi issue.
-
This has been making my life difficult too, lately.
I think for me it's mainly that the page titles are being used for auto-complete as well as URLs - but I'm not sure.
I've turned off auto-complete for now, AND tweaked the other settings, but it's not right. I definitely had auto-complete on before, and the suggestions were as I expected, and recently they became unusably polluted. -
Yes, this is frustrating. Address bar does some very weird things now. Hopefully this will be fixed, this is first time I get so annoyed with Vivaldi so I'm surprised. Address bar with this behavior is a deal braker for me.
-
Still an issue as of 5.5.2805.42.
-
Weighted auto-complete has been a browser feature since ancient times.
This must be a regression due to recent address bar changes.
@nelliott500
If it does not get fixed, you can inquire about the status here:
https://forum.vivaldi.net/topic/27450/what-is-the-status-of-vb-already-reported-bug-issue?page=1 -
https://forum.vivaldi.net/post/621760
Confirmed a bug and will be fixed in a future release.
-
For those wondering, the 2893.3 snapshot doesn't fix it.
-
Very unfortunate but thank you for the update.
-
This is infuriating. The auto-complete is super aggressive and I have to delete something every time I use the address bar. Is there any way to go back to a previous version of Vivaldi?
-
I saw this post https://forum.vivaldi.net/topic/3934/url-autocomplete from 2015 that hadn't been fixed and had been archived in 2021. Has this been fixed yet? This is absolutely the most annoying thing about Vivaldi for me. When I type "red" I want it to autocomplete "reddit.com" not "reddit.com/r/random_subreddit/some_link_I_looked_at_last_week/" and When I type "you" I want it to autocomplete "youtube.com" not "youtube.com/?watch=whatever_video_I_last_watched".
This is standard DEFAULT behavior on Chrome and Firefox, why is it not in Vivaldi, and why has it not been fixed since 2015?!?
-
It hasn't been an issue since 2015. This is a new issue as of 5.5.2805.35. I've already created a thread on this (there are others as well) and it has been confirmed a bug that will be fixed in a future release.
