Bug 112777 - Writer initial screen elements not sized to display
Summary: Writer initial screen elements not sized to display
Status: RESOLVED DUPLICATE of bug 107764
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
5.4.1.2 release
Hardware: Other Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-09-30 15:49 UTC by dstrawser55
Modified: 2017-10-01 22:29 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
Screen capture of initial Writer screen (183.36 KB, image/png)
2017-09-30 15:49 UTC, dstrawser55
Details

Note You need to log in before you can comment on or make changes to this bug.
Description dstrawser55 2017-09-30 15:49:23 UTC
Created attachment 136646 [details]
Screen capture of initial Writer screen

New Windows 10 on new laptop with 13.5 inch screen 3000 x 2000.

 Launch LibreOffice.
 1. The initial screen is not laid out correctly. Bottom of window is cut off so the information bar is cut and problematic to read or use the resize slider.
 2. Icons on top row of icon bar are partially cut off on top; this is due to the title bar overlapping on them.
 3. Hovering over icons to display tooltips is way off. Can be quite far from the icon and the tooltip is displayed. In fact, for the top icon row, hovering directly on the icon produces no tooltip. Hovering directly on an icon on the 2nd row produces the tooltip for the icon ABOVE it on the TOP row!
 4. I attached a screen capture; this is the full screen area, not a portion or cropped in any way.

I am a long-time user of MS Office. However, I would REALLY like to like LibreOffice so that I do not have to use MS Office on this new laptop. But these issues are a productivity killer for me, so unless you have a fix, I have to go to another app.
Comment 1 Xisco Faulí 2017-10-01 22:29:26 UTC
Thanks for reporting this issue.
It seems like a duplicate of bug 107764
Regards

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