nextcloud / nextcloud/tasks

[Feature request] Disable capture of Ctrl+F keyboard shortcut

Open Beginner friendly
#3,240 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
JavaScript
Stars
706
Forks
117
Avg merge
8h 50m
Merged PRs (30d)
18

Description

Is your feature request related to a problem? Please describe.

In Tasks view, I often want to search for a term in the task titles.

Normally, I would press Ctrl-F, which is the Find in page keyboard shortcut in most browsers. Then I would enter the search term and press Enter. This is a familiar, efficient workflow that accords with habit and muscle memory.

Nextcloud Tasks breaks that workflow, because it intercepts the Ctrl-F keyboard shortcut, so that instead of launching the browser's Find in page feature, it instead launches Nextcloud's Search dialogue.

This violates the UX/UI principle of least surprise.

Nextcloud's Search dialogue doesn't just search the contents of the page (which is what the user would expect after hitting Ctrl+F in a web browser). It instead searches the user's entire Nextcloud account, and can be quite slow about it!

This means that a Nextcloud Tasks user has to choose between two slow, unpalatable, friction-inducing options:

  1. Switch to the mouse (a problem in itself for some disabled users) and labouriously access the browser's Find in page function by manually clicking through the relevant browser toolbar menus.
  2. Wait for the Nextcloud Search to load, and then wait again for it to perform its search (which typically gives more results than the user wants, e.g. calendar events, documents, etc), and then wait yet again for it to navigate to the task of interest once selected.
Describe the solution you'd like

Ctrl-F should not be intercepted by Nextcloud Tasks.

Describe alternatives you've considered

If it is still desired to have a keyboard shortcut for Nextcloud Search from Nextcloud Tasks, then it should be something other than Ctrl-F.

For instance, it could be Ctrl-Shift-F.

Additional context

No response

Contributor guide

Open the contributing guide

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.

Research direction

Start by locating the Tasks view keyboard-shortcut handler for Ctrl-F and the code that opens Nextcloud Search. Reproduce the shortcut in Tasks view, then verify that Ctrl-F invokes the browser's Find in page instead; if an alternate search shortcut is retained, check that it still opens Nextcloud Search. Done means Ctrl-F is no longer intercepted.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Feature
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Clearly specified
Newbie friendliness
70/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.