Omnibox - Allow Suggestions to Appear Based on #match |
|||
Issue descriptionChrome Version: (copy from chrome://version) OS: (e.g. Win7, OSX 10.9.5, etc...) What steps will reproduce the problem? (1) visit forbes.com and click on a top headline. e.g. I ended up navigating to: (2) https://www.forbes.com/sites/danalexander/2017/03/29/putin-vladimir-donald-trump-russia-billionaires-oligarchs/#4495706643f9 (3) Open new tab, type '4495706643f9' and then type 'billionaires' What is the expected result? Both are unique enough to autocomplete the URL just visited What happens instead? Only 4495706643f9 is - in fact I can't get any of the words in the URL to trigger the omnibox autocomplete Please use labels and text to provide additional information. For graphics-related bugs, please copy/paste the contents of the about:gpu page at the end of this report.
,
Mar 29 2017
sorry, yes they were (corrected in post, I think).
,
Apr 14 2017
I'm happy to share I'm currently running an experiment with a revised algorithm, and one of the knobs I'm trying would allow these weak matches to be displayed. Hopefully in a month I'll have more news to share. I need some more data to decide whether the something it's doing is actually the right something. :-)
,
Aug 2 2017
I recently submitted a change ( https://chromium.googlesource.com/chromium/src.git/+/fbc743ee8228f50c12e466a440f2920f3c86d5b8 ) that fixes this bug! Thanks for the report--I used it as a test example in my experiments. The fix is submitted for Chrome 62. I also rolled it out via Chrome's experiment framework to all stable channel users. (I used the framework to prove that this change is good for users. Now I turned the "experiment" up to 100%.) The next time you restart your browser, you should see the new behavior. Please file new bugs if you have additional feedback/complaints. Thanks! |
|||
►
Sign in to add a comment |
|||
Comment 1 by pkasting@chromium.org
, Mar 29 2017