Option to move search engine suggestions into adress bar.
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 15/100
Research direction
The issue names no files, tests or entry points, so start by finding where the address bar and search suggestion list are implemented in the Dart/Android codebase. The request is a UI behaviour change (a search-engine icon that lights up when suggestions exist and switches engines on tap), and it has no comments or maintainer decision yet. Done would mean the maintainers agree on the interaction design first, and only then an implementation.
Written by the indexing model from the issue text.
Description
Whenever we want to use search engine suggestions we need them to be very close to adresss bar, but when we dont need them we want them to not be visible and not take space and not distract. So i think i have an idea how to do it.
When we click on search engine suggestion it brings icon, but on default search engine there is no icon, and adress bar is clean. We could utilize that.
Lets imahine google is our default search engine. We need to have have search engine icon always visible. We for example start to type "wikip". Search engine suggestion detects possible suggestion, and list is not empty. At that moment search engine icon's outliner (google icon in our case) lights up, and we know wr have search engine suggestions avialable. We click google icon and from popup or drop down list choose wikipedia, and icon changes to wikipedia. But if we dont want to use search enhine suggestions we can ignore glowing animation, and use other suggestions that will be immediatelly under adress bar.
- Dominant language
- Dart
- Stars
- 1k
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 FaFre/WebLibre
-
bug enhancement needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
enhancement needs-triage
Difficulty 3/5 1-2 days Newbie friendliness 60/100
-
enhancement needs-triage
Difficulty 5/5 Over a week Newbie friendliness 8/100
-
bug enhancement needs-triage
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
needs-triage
Difficulty 4/5 1-2 days Newbie friendliness 48/100
Similar issues
-
bug from-telegram platform:windows
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
hiddify/hiddify-app#2592 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
cogwheel0/conduit#1122 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
bannzai/shoppinglist#779 ·
Maintainers usually reply within 1 day
-
Android bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
PostHog/posthog-flutter#731 · 1 comment ·
Maintainers usually reply within 1 day
-
[BUG] JEFIT import fails because # characters are not recognisedPossibly taken A pull request linked to this issue is open or already merged. Openbug
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day