-
-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
CTRL+F in a text file does not seem to work any more #5198
Comments
Yeah the editor brings up it's own search for me: However, if you have an issue with this or think it should change, please open your issue in the repo of the app: https://github.com/nextcloud/files_texteditor |
Please don't close this like this. It does not bring the editor own search for me. I did not remember there was such a feature in the editor of the web interface of nextcluod itself. Otherwise I wouldn't have filed this issue at all if the "find" feature was working in any way. (See the bug report below, "Steps to reproduce" point 3 "Nothing happens" ie there is no editor find feature appearing). Bug report updated above to reflect the fact that there is no editor find feature working. Edited: didn't see the comment below the screenshot. See nextcloud/files_texteditor#39 |
I can confirm that the text editor does not open a search box if CTRL +F is pressed. Here is the error log from the browser:
The problem appears using Nextcloud 12 with Firefox 54.0.1. The problem does not happen in Vivaldi 1.10, here the search bar of the browser is opened and works well. |
I am also getting this issue. Upon checking the Chrome dev console, the problem appears to be an incorrect MIME type for the searchbox:
This error is thrown every time I hit CTRL+F in a text file. |
Steps to reproduce
Expected behaviour
Actual behaviour
The editor seems to hijack the CTRL+F binding and prevents the browser built-in find feature from working.
The editor does not replace this with its own find feature.
Should be easy enough to reproduce, tested with very different configs by different people who could reproduce (Windows, Mac, etc.).
The text was updated successfully, but these errors were encountered: