Adjust autocomplete and priority inside omnibox with bias towards most used websites
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
Research direction
Start by locating the omnibox autocomplete code and how it ranks history results. The issue proposes tracking how often users open or switch to each domain, then favoring domains whose names begin with the entered keyword at any level. Define completion by matching the described “ama” example and ensuring visit count, rather than pages viewed in one visit, drives popularity.
Written by the indexing model from the issue text.
Description
The problem
Currently, when you start typing in the omnibox (Cmd+T), it prioritizes Google search over the most popular domain in your history.
Let's look at this example and comparison to Arc:
When i begin typing "ama", I see this:
While it does see that I visited Amazon in the past, it places Google Search at the top and amazon.com all the way at the bottom.
At the same time in Arc:
And what is interesting, Safari follows the same practice:
What you'd like
There needs to be a collection of domains and their historical popularity. While a ranking from history might be better than current behavior, I believe it's better to count openings or switches to the domain. In this case, domains that you visited once but looked through 100 pages do not outweigh a website that you visited 50 separate times.
And to be clear - entered keyword myst be exact start of the domain at any level (subdomain, domain, etc).
- Dominant language
- Swift
- Stars
- 648
- Forks
- 56
- Avg merge
- 21h 14m
- Merged PRs (30d)
- 22
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from yetanotherbrowser/yab
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
yetanotherbrowser/yab#1008 ·
Maintainers usually reply within 2 days
-
area: passwords Broken bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
yetanotherbrowser/yab#923 ·
Maintainers usually reply within 2 days
-
bug needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
yetanotherbrowser/yab#918 · 1 reaction ·
Maintainers usually reply within 2 days
-
iPhone: the + button and the checkmark sit on top of the Space switcher in the bottom barPossibly taken @ChaseRoofener claimed this 3 days ago. OpenAnnoying area: iphone bug needs info
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
yetanotherbrowser/yab#915 · 3 comments ·
Maintainers usually reply within 2 days
-
CONTRIBUTING.md and CI run scripts/runs/tests_for.py, which is not in the repositoryPossibly taken @serafimcloud claimed this 2 days ago. OpenAnnoying in progress
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
yetanotherbrowser/yab#875 · 1 comment ·
Maintainers usually reply within 2 days
All issues in yetanotherbrowser/yab
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
haacked/switchboard#460 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
manaflow-ai/cmux#47572 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
borrowcheckmate/swimlie#48 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Ranchero-Software/NetNewsWire#5572 ·
Maintainers usually reply within 11 days
-
api beginner story
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
NCSU-App-Development-Club/ios_fall_26#86 ·
Maintainers usually reply within 4 days