Adjust autocomplete and priority inside omnibox with bias towards most used websites

Open
#971 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
swift
Domain
desktop, search

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

area: command Polish proposal
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:

SCR-20261117-skpz

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:

SCR-20261117-slac

And what is interesting, Safari follows the same practice:

SCR-20261117-slfq
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

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from yetanotherbrowser/yab

All issues in yetanotherbrowser/yab

Similar issues

More Swift issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.