Feature #86761
closed
"CTRL-F" to search in the backend window and in open files
0%
Description
If you work on a CSS-file most of the time you want to change a certain class.
In LTS 8.7 having a fileadmin file open (e.g. CSS-FILE) you just pressed "CTRL-F" to search the backend window AND inside the open file. This was fast and easy, because it put you directly inside the css-file at the spot you wanted to work on.
Now you have to activate the already open file-window inside the backend-window first with a mouse click, an then activate the new inside-the-file-search with a "CTRL-F" to then search insde the open file.
Okay, it is just one click more, but for people who are so used to the old easy system you always activate the BE-Window-search and then instead of typing a search command you then type at a random spot inside your open document a class name insted a search phrase at a search window. This leads to a lot of confusion and destroys the rhythm people developed over years.
It will probably also lead to some funny bugs inside css files if experienced integrators are relying on their trained skills/habits.
Files
Updated by Wouter Wolters over 5 years ago
- Subject changed from LTS 9 – "CTRL-F" to search in the backend window and in open files to "CTRL-F" to search in the backend window and in open files
Updated by Wouter Wolters over 5 years ago
- Target version deleted (
Candidate for patchlevel)
Updated by Georg Ringer over 5 years ago
- File Bildschirmfoto 2018-11-01 um 20.22.55.png Bildschirmfoto 2018-11-01 um 20.22.55.png added
- Status changed from New to Needs Feedback
Sorry don't really understand the issue. browser search still works for me in master as well, see attachment.
Updated by Thomas Hezel over 5 years ago
- File browser-search.jpg browser-search.jpg added
Did more testing:
If you see the target in the window then the browser search works.
If the target is not visible in the window (you have to scroll) browser search doesn't work only the new document search works.
It's not a major issue just a bit against old habbits.
The bigger issue is, that after "save" the document goes to line 1.
Updated by 
Updated by Benni Mack about 4 years ago
- Sprint Focus changed from PRC to Needs Decision
Updated by Christian Kuhn about 2 years ago
- Status changed from Needs Feedback to Closed
Hey. I hope it's ok to argue that writing and maintaining site-related code like css files within fileadmin is not a good habit. such stuff should be located in a site extension and probably developed with an IDE that is crafted to handle such stuff.
The file edit module for fileadmin files is more an editor thing so editors can edit simple things like a .txt file or similar. I'd say the current usablitity is ok'ish for these kind of editor task.
I hope it's ok to close here for now - the editor experience can of course be improved in this area, but maybe we want to restart such as task with a patch in a fresh issue.