Search selected/entered via omnibar on background #1770
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Sometimes it feels natural to accumulate links in the background to read them later.
Solves #1757
Functionality is ready but I want to discuss defaults and some refactorings.
What should be the default key for searching in the background?
I choose
;
because it's unlikely to someone assignsearchAlias
to;
.b
for "background" is occupied by default and even if the user changes it'll probably clash with Baidu or Bing.Should we refactor?
I think it's sufficiently hard to grasp which line adds what functionality in the current state.
For
o
+alias
likeog
for "Open Google"Control + Enter
opens in background so one Omnibar is enough. But other parts have some repetitions, we can use some kind of builder, but to use a builder we need to changesearchSelectedWith
to something likesearchSelectedWith(URL: string, options: {})