Bug 121047 - Alignment issue regarding placement of buttons in the Find & Replace dialogue box of LibreOffice Writer
Summary: Alignment issue regarding placement of buttons in the Find & Replace dialogue...
Status: RESOLVED DUPLICATE of bug 113132
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.1.2.1 release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-10-30 02:19 UTC by Gaurav Sharma
Modified: 2018-10-30 13:27 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Attachments
Photo showing improper alignment of certain buttons (106.02 KB, image/png)
2018-10-30 02:22 UTC, Gaurav Sharma 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Gaurav Sharma 2018-10-30 02:19:18 UTC 
Description:
When we start LibreOffice and go to the Find & Replace dialogue box and click Format button to open another dialogue box, the alignment of the certain buttons in the Find & Replace dialogue box gets changed and is improper as certain buttons gets overlapped. This has been particularly observed when we go to the Find & Replace dialogue the first time.

Steps to Reproduce:
1. Open Writer.
2. Open the Find & Replace dialogue box.
3. Click the Format button.
4. Choose a format and click OK.
5. You will see that the alignment of certain buttons gets changed improperly. Overlapping will be seen.

Actual Results:
You will see overlapping of buttons in the Find & Replace dialogue box.

Expected Results:
The alignment of buttons should have been proper in the Find & Replace dialogue box.


Reproducible: Always


User Profile Reset: No



Additional Info:
Comment 1 Gaurav Sharma 2018-10-30 02:22:14 UTC 
Created attachment 146155 [details]
Photo showing improper alignment of certain buttons
Comment 2 Dieter 2018-10-30 13:27:56 UTC 

*** This bug has been marked as a duplicate of bug 113132 ***