You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Summary
The new URL bar is great for launching things by name (extensions, spaces, etc.), but I can’t find a way to scope results to extensions only. Results are always mixed, and I have to type the full extension name to see it (often not even as the first result). At that point, it’s faster to open the extension manually.
Steps to Reproduce
Update to v1.16b.
In the URL bar, start typing the name of an installed extension.
Observe that results include many categories (web results, history/bookmarks, spaces, commands), and the extension is not ranked first unless you type the full name.
Expected Behavior
A way to filter/scope the search to extensions only, so only extensions appear in results.
Exact/prefix matches for extension names should be ranked at the top when the scope is “extensions”.
Actual Behavior
I don’t see a documented way to scope results to extensions.
Extension matches are often not ranked first even for near-exact prefixes.
Questions
Is there an existing shortcut or operator to filter only extensions?
For example, something like:
e:<name> (e.g., e:ublock)
@ext <name>
A keyboard shortcut that pre-fills the scope (e.g., Ctrl+E → e:)
Feature Request / Proposals
Scope operators in the URL bar:
e: = Extensions
s: = Spaces
b: = Bookmarks
h: = History
t: = Tabs/Windows
c: = Commands/Actions
When a scope operator is present, hide non-matching categories completely.
Ranking improvements (within or without operators):
Exact and prefix matches for extension names should be ranked first.
If an operator is used (e.g., e:), other categories should be excluded, not just demoted.
UI affordances
Optional “chips”/toggles above the results to quickly constrain by category (Extensions, Spaces, Bookmarks, etc.), navigable via keyboard (Left/Right to switch chip).
Visual hint in the bar (ghost text) showing available operators after typing the first character.
Settings
“Prefer extension matches when typing extension names” (promote to top).
“Remember last scope for this session.”
Optional: disable cross-category suggestions when a scope is detected.
Keyboard
Shortcut to cycle scopes (e.g., Ctrl+1/2/3… or Alt+[ / Alt+]).
Shortcut to pre-fill operator (e.g., Ctrl+E inserts e:).
Workarounds considered
If there is a hidden command, about:config flag, or an existing keyboard shortcut to scope to extensions, please point me to it.
Why this matters
The URL bar becomes a reliable command palette: faster, predictable, and learnable.
Power users can keep hands on the keyboard and avoid full names and mixed lists.
Thanks for the great update and for considering these improvements!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Summary
The new URL bar is great for launching things by name (extensions, spaces, etc.), but I can’t find a way to scope results to extensions only. Results are always mixed, and I have to type the full extension name to see it (often not even as the first result). At that point, it’s faster to open the extension manually.
Steps to Reproduce
Expected Behavior
Actual Behavior
Questions
For example, something like:
e:<name>
(e.g.,e:ublock
)@ext <name>
Ctrl+E
→e:
)Feature Request / Proposals
Scope operators in the URL bar:
e:
= Extensionss:
= Spacesb:
= Bookmarksh:
= Historyt:
= Tabs/Windowsc:
= Commands/ActionsWhen a scope operator is present, hide non-matching categories completely.
Ranking improvements (within or without operators):
e:
), other categories should be excluded, not just demoted.UI affordances
Settings
Keyboard
Ctrl+1/2/3…
orAlt+[
/Alt+]
).Ctrl+E
insertse:
).Workarounds considered
Why this matters
Thanks for the great update and for considering these improvements!
Beta Was this translation helpful? Give feedback.
All reactions