Request: Improve usability of the search function

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

Maintainers usually reply within 1 day

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
Stale
Domain
frontend, search

Research direction

Start by tracing the search function and search panel, then compare how the Tracks and Favorites panels handle focus and closing. Verify the intended keyboard entry points for opening, focusing, and closing each panel. Done means search opens from a global shortcut with its field focused, Esc closes it, and equivalent shortcuts work for the other named panels.

Written by the indexing model from the issue text.

Description

Nice to have

Since map objects are not directly clickable, they must first be found using the search function, e.g. to make them a favorite. For this reason, the search must be used very frequently and is currently associated with a large number of clicks.

The following would improve this:

  • Introduce a global keyboard shortcut for search (e.g. F3). It would also be nice if all panels (Tracks, Favorites etc.) had a shortcut.
  • The focus should then be placed directly in the search field. Currently, this still has to be clicked before the search text can be entered.
  • It should be possible to close the search panel using the keyboard (e.g. Esc key). This requirement also applies to the other panels (Tracks, Favorites etc.).

Thanks for considering this feature request.

Dominant language
MDX
Stars
63
Forks
431
Avg merge
17h 10m
Merged PRs (30d)
124

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

  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 osmandapp/web

All issues in osmandapp/web

Similar issues

More Web Dev issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.