Group similar results together
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 27k
- Forks
- 2.6k
- PR merge metrics
- No merged PRs in 30d
Description
In the above screenshot, I am trying to use the omnibar to search using my configured search engine. I think the behaviour that a user might expect would be that suggestions of a certain type would be grouped together (like search suggestions first, then suggestions from currently open tabs, and then suggestions from history). But here we can see that some search suggestions come in between the history suggestions and a lot of times even suggestions for currently open tabs do come up in between.
While this isn't a major problem, more than once I have carelessly opened results from my history instead of opening the search engine as I intended to. I am not sure if this is the intended behaviour or not, but if it is I'd like to know what the order of suggestions is based on.
Contributor 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.
Research direction
The issue names no files or tests. Start by locating Vimium’s omnibar suggestion collection and ranking logic, then inspect how search, open-tab, and history suggestions are interleaved. Done means similar suggestion types are grouped consistently, with coverage for the ordering behavior described in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100