https://bugs.documentfoundation.org/show_bug.cgi?id=165956
Eyal Rozenberg <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |UNCONFIRMED Resolution|WONTFIX |--- --- Comment #4 from Eyal Rozenberg <[email protected]> --- I'm challenging the WF, drawing your attention to the fact that the ask is either for a visible-by-default or invisible-by-default toggle, which wont the "complexity" argument is side-stepped entirely. Remember that the find bar is often used to search when you want the dialog not to obstruct the document contents. User should not be required to choose between search capability and result inspection convenience. Also, let us recall "find bars"/"find pop-ups", used in most popular applications which support regexp search at all - typically _do_ have regexp capability. This is true in particular for text editors, such as Sublime Text, gEdit, Featherpad, VS Code, JetBrains IDEs, etc. (Of course, it is off by default.) So, people are used to this "complexity", and those app authors have determined it is merited. About the complexity, I'll also challenge the claims made here: * "Find bars"/pop-ups in most applications I know, which support regexp search at all, typically _do_ have regexp capability. This is true in particular for text editors, such as Sublime Text, gEdit, Featherpad, VS Code, JetBrains IDEs, etc. (Of course, it is off by default.) So, * The "complexity" is only there if the user cares to explore it. They don't have to worry about widgets others than the search box, if they don't want to. * "simple quick find" - using regular expressions _is_ simple and quick, when you know how to use them. Finally, I want to draw your attention, Heiko, to the fact that none of the opponents of this suggestion made an attempt to rebut the use-case/motivation. -- You are receiving this mail because: You are the assignee for the bug.
