-
Notifications
You must be signed in to change notification settings - Fork 138
Search (Ctrl+F) trap for searching files (rather than text) is not useful #268
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Sounds reasonable. |
@korelstar It should be deactivated by default, so I assume there is some code that sets this up in this app. |
No, I don't think that we activate the shortcut manually. Instead, it's activated by the Nextcloud core when providing a search using the search API: An option would be to add an option to the search API, that doesn't add the listener when the option is set. |
I think pressing ctrl f a second time opens the browser default search, can someone confirm this? |
@stefan-niedermann that indeed works! I guess it can be closed then. |
There is a trap in Notes for Ctrl+F which does not allow text searches in a file, it then searches for files. This is not ideal or useful. Please introduce a different trap for this, e.g. Ctrl+Shift+F, please don't break regular browser workflows.
The text was updated successfully, but these errors were encountered: