Bug 125163 - Wrong arrows in "find" toolbar
Summary: Wrong arrows in "find" toolbar
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.1.5.2 release
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-05-07 19:10 UTC by J22Gim
Modified: 2020-02-11 13:30 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
everything seems ok (56.41 KB, image/png)
2019-06-10 16:02 UTC, BogdanB
Details
no bug (14.12 KB, image/png)
2019-12-08 19:12 UTC, BogdanB
Details

Note You need to log in before you can comment on or make changes to this bug.
Description J22Gim 2019-05-07 19:10:53 UTC
Description:
When I search a phrase or word, the "find toolbar" appears. Next to the search field there are two arrows (text is from the tooltip text): 
1) "Click to search the next occurrence in upward direction"
2) "Click to search the next occurrence in downward direction"

The problem is, 1 is a DOWNWARD arrow and 2 is a UPWARD arrow!

Steps to Reproduce:
1. Open any writer file with text
2. CTRL+F to open the "find" toolbar
3. see the arrows and the description mentioned in the tooltip 

Actual Results:
Default: 
1) Downward arrow is to "Find previous"
2) Upward arrow is to "Find next"

Extend tip in the Tools-Options-Libreoffice General mark "Extended tips"
1) Tooltip for Downward arrow is "Click to search the next occurrence in upward direction"
2) Tooltip for Upward arrow is "Click to search the next occurrence in downward direction"

Expected Results:
I think first we need to agree on a very basic thing, that is a writen document GROWS DOWNWARD as more pages are added at the END of the document, ok?.
If this is true, then if you want to find the "next" occurrence of anything, by default you would look for it in the text to the right and BELOW the cursor, right? If this is true, then there should be a functional equivalence between these terms: NEXT=DOWNWARD and PREVIOUS=UPWARD

If that is true, then the downward arrow should work to search for (a NEXT) something DOWNWARD, and the upward arrow should work to search for (a PREVOIUS) something UPWARD.

It is exactly the opposite as what I see.


Reproducible: Always


User Profile Reset: Yes



Additional Info:
Note: I have elementary icons

Version: 6.1.5.2
Build ID: 1:6.1.5-0ubuntu0.18.10.1
CPU threads: 4; OS: Linux 4.18; UI render: GL; VCL: gtk3_kde5; 
Locale: en-US (en_US.UTF-8); Calc: group threaded
Comment 1 Dieter 2019-05-07 20:09:00 UTC
Thank you for reporting the bug. Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version. Change to RESOLVED WORKSFORME, if the problem went away.
Comment 2 BogdanB 2019-06-10 16:02:01 UTC
Created attachment 152081 [details]
everything seems ok

Can NOT confirm this bug.

I tested with Elementary icon on
Version: 6.1.6.3
Build ID: 5896ab1714085361c45cf540f76f60673dd96a72
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk2; 
Locale: ro-RO (ro_RO.UTF-8); Calc: group threaded

This is a very near version with that reported, but the arrow are ok, like they should be.
Comment 3 QA Administrators 2019-12-08 03:45:56 UTC Comment hidden (obsolete)
Comment 4 BogdanB 2019-12-08 19:12:22 UTC
Created attachment 156413 [details]
no bug

I tested again on 6.5 with elementary icon.
I can NOT see any problem.
See the screenshot.

Version: 6.5.0.0.alpha0+
Build ID: 5030be4e85179147476b1e441eb618fb6ed58235
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; 
TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2019-11-28_20:14:48
Locale: ro-RO (ro_RO.UTF-8); UI-Language: en-US
Calc: threaded

J22Gim, please try a new version and see if there the bug persist.
Comment 5 J22Gim 2020-02-11 13:12:37 UTC
Checked again with Version: 6.4.0.3
Works fine!
Comment 6 Dieter 2020-02-11 13:30:38 UTC
(In reply to J22Gim from comment #5)
> Checked again with Version: 6.4.0.3
> Works fine!

=> RESOLVED WORKSFORME