CTRL+F in a text file does not seem to work any more

[hugoroy]

Original: nextcloud/server#5198

Steps to reproduce

1. Go to a text file and open it with the Nextcloud server web interface editor (url like https://nextcloud.example.org/index.php/apps/files/?dir=/directory&fileid=11118#editor )
2. Press CTRL+F (Chrome, reproduced with Firefox, Mac / Windows / Linux)
3. Nothing happens

Expected behaviour

1. Go to a text file and open it with the editor
2. Press CTRL+F
3. Get a "find" feature (either the browser's built-in find feature, or a custom Nextcloud's web interface editor find feature)

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.).

Nextcloud version: 12.0.0.29
Texteditor version: 2.4.1

[agrudsky]

+1 - how has there been no activity on this issue? I am also experiencing the same thing. Whenever I press CTRL-F in a Nextcloud text document, no find box pops up, and here's what I get in the Chrome console:

GET https://nextcloud.example.com/apps/files/ext-searchbox.js net::ERR_ABORTED

[kralizeck]

Same here, but i found a quick-and-dirty solution.

NC 12.0.4
Texteditor 2.4.1

On web server log there is a reference to:
..."GET /apps/files/ext-searchbox.js HTTP/2.0"...

that file doesn't exist. Searching, it is at
/apps/files_texteditor/js/core/vendor/ace-builds/src-noconflict/ext-searchbox.js

so, I create a symbolic link on /apps/files/
ln -s ../files_texteditor/js/core/vendor/ace-builds/src-noconflict/ext-searchbox.js

reloaded web server and Crtl+F worked as expected.

I doesn't have code skill to find where is the problem. :(

[agrudsky]

@kralizeck - thank you! I have followed the steps you outlined and it is working as expected for me as well. I appreciate you posting the steps.

I find it ridiculous how the Nextcloud dev team is completely ignoring this issue. Don't get me wrong, I am extremely grateful for the hard work they put in, and for it being provided for free - but this issue has been open for over six months without so much as an acknowledgement from the developers. I hope that we can see this fixed soon in the next updates for Nextcloud.

[jancborchardt]

@nextcloud/javascript could someone look into this bug?

[danxuliu]

could someone look into this bug?

Fix (for master) is in #82; a backport to fix it in Nextcloud 12 is in #84.

[MorrisJobke]

Fixed by #82

[hugoroy]

Thanks!! Le 7 février 2018 20:36:02 GMT+01:00, Morris Jobke <notifications@github.com> a écrit :

…

Closed #39.

-- Envoyé de mon appareil mobile Sent from my mobile device