Using 5.0.2.2, build ID: 37b43f919e4de5eeaca9b9755ed688758a8251fe on a Mac. Steps to reproduce: 1. Open just about anything. Even an empty, new spreadsheet does the trick. 2. Press Ctrl+F. 3. Type anything into the search bar that will NOT be found. 4. Press Enter. Expected result: An immediate message saying "Search key not found". Actual result: Nothing, unless the mouse is hovered on the search bar (anywhere). Mitigation factor: If any of the arrow buttons are clicked with the mouse, the message appears immediately.
The message also appears after pressing "Enter". Not sure what's to be expected here. Of course it would be great to see results as you type away your search. In my test, the arrow keys do not trigger the info "No search results found" but allow to skip through previous searches or move forward / backward amongst those. Comparing with Firefox, that one immediately shows all search results as the user type their search in the searchbar. Setting to NEW - Enhancement and adding "UX-advise" for input as to what is expected here.
I'm not expecting instant search results while I'm typing. I'm expecting a "Search key not found" message after I press Enter, which is not displayed. If I click on the arrow buttons with the mouse instead, I get that message displayed. If I move the mouse over the search bar after pressing Enter, I get that message displayed. If I press Up/Down keys on my keyboard, I can navigate between my previous search keys, but that has nothing to do with my bug report.
In that case I cannot confirm this bug. I get that exact result. 1. Empty writer document 2. cmd + f to open search 3. type 123 4. press enter "No search results found" message on the right side of search bar. Back to Unconfirmed thus. 5.0.2.2 + OS X 10.11 here.
can't confirm this either, Laszio. Sometimes, depending on config and theme, displayed text is very hard to see. Could that be the case for you too? Cheers - Cor
Cor, I think you’re referring to bug 89760 – but that’s Linux-only. OP’s OS is Mac.
(In reply to Cor Nouws from comment #4) > Sometimes, depending on config and theme, displayed text is very hard to see. > Could that be the case for you too? No, that's not the case for me, because I can see the text clearly when I use the up/down arrow buttons next to the textfield, or when I hover over the search bar with the mouse.
No repro Version: 5.0.2.2 Build ID: 37b43f919e4de5eeaca9b9755ed688758a8251fe Locale : fr-FR (fr.UTF-8) OSX 10.11 when I type in any string and press enter in the search dialog in an empty Writer document, I get a "Expression not found" message immediately.
@laszio : which version of OSX are you using ?
(In reply to Alex Thurgood from comment #8) > @laszio : which version of OSX are you using ? I'm using OSX Yosemite 10.10.5. Oh, and I haven't tried it before, so I just did it: this problem appears in Writer, too. Reproduction steps are described in comment #7.
Sorry I can't follow this. Comment 7 says "can't repro". Thenbug reporter says repro steps are in comment 7. What? I couldn't reproduce as stated earlier. This bug is getting really confusing. I still can't reproduce (neither could Alex). Laszlo: could you please create a screencast (if you have no tool you can do that with the onboard quicktime software) showing this issue. After providing that, please set the bug back to UNCONFIRMED.
Created attachment 120005 [details] Search bar showing a wrong result for the first cell Version: 5.1.0.0.alpha1+ TinderBox: Win-x86@62-merge-TD Fiddling around I was able to "wrap" the message to the left most position of the search bar but not in a reproducible way. However, it is cleared on refresh (just resize the form, for instance) what might result in trouble on Mac OS X. I suggest to not just draw onto the canvas but to use a normal label (which paints itself properly). And by doing so the vertical alignment could be improved too. Aside from this issue there are some more issues. "Reached the end" for 'result found' is sketchy but "not found" when the first cell is selected is a bug. You should also make sure to use the right icon. The grey X looks suspicious.
We're replacing our use of the 'ux-advise' component with a keyword: Component -> LibreOffice Add Keyword: needsUXEval [NinjaEdit]
Ticket is in state NEEDINFO for over one year. Closing now.