Bug 117267

Summary: UI - Dialogs do not have a marker that they are to small
Product: LibreOffice Reporter: Thomas Krumbein <tk>
Component: UIAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal CC: telesto, xiscofauli
Priority: medium    
Version: 6.1.0.0.alpha0+   
Hardware: x86-64 (AMD64)   
OS: Windows (All)   
Whiteboard:
Crash report or crash signature: Regression By:
Attachments: Pic 01 - standard option dialog size
pic 02 - resized dlg-size - more options
pic 03 - different behaviour - options not readable in standard size

Description Thomas Krumbein 2018-04-27 06:54:31 UTC 
Description:
Playing with LO 6.1.0.0 alpha on Win 10 Option Dialogs have a default size. Unfortunately not all Options will be displayed in this size - and there is no indicator, that some options are not displayed.

Missing srollbars or something else.


Steps to Reproduce:
1.new profile, open a modul i.E. Writer, open options
2.use Writer - formating
3.see screenshots

Actual Results:  
screen o1 - standard size of option-dialog - there are some more options, not displayed. 

Enlarge dialog - options will be displayed.

Different behavior in option "Änderungen" (change management??) - options will be displayed, but unreadable - see pic 3.

Expected Results:
see pics


Reproducible: Always


User Profile Reset: Yes


OpenGL enabled: Yes

Additional Info:


User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:59.0) Gecko/20100101 Firefox/59.0
Comment 1 Thomas Krumbein 2018-04-27 06:55:28 UTC 
Created attachment 141668 [details]
Pic 01 - standard option dialog size
Comment 2 Thomas Krumbein 2018-04-27 06:56:07 UTC 
Created attachment 141669 [details]
pic 02 - resized dlg-size - more options
Comment 3 Thomas Krumbein 2018-04-27 06:57:03 UTC 
Created attachment 141670 [details]
pic 03 - different behaviour - options not readable in standard size
Comment 4 Thomas Krumbein 2018-04-27 06:58:09 UTC 
test is LO 6.1.0.0.Alpha 1!!
Comment 5 Xisco Faulí 2018-04-27 13:36:21 UTC 
Thanks for reporting the issue.
I'd say it due to the problem described in bug 117288

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