See screenshot. On launch, the window comes up centered. It shouldn't per Mac OS X guidelines (and likely other platforms as well).
It should be positioned at the left edge of the screen immediately below the menu bar. Furthermore it should, at least on small screens like 13" laptops, be maximized.
FYI Microsoft Word gets this right.
Steps to Reproduce:
1. Launch LibreOffice
centered, not maximized
not centered, maximimzed
User Profile Reset: No
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.113 Safari/537.36
Created attachment 136029 [details]
Created attachment 136030 [details]
new document window
(In reply to Elliotte Rusty Harold from comment #0)
> See screenshot. On launch, the window comes up centered. It shouldn't per
> Mac OS X guidelines (and likely other platforms as well).
> It should be positioned at the left edge of the screen immediately below the
> menu bar. Furthermore it should, at least on small screens like 13" laptops,
> be maximized.
Strange ideas. Wrong in Linux case.
Best regards. JBF
@Elliotte : Unfortunately, LibreOffice is still quite far from being a nicely behaved macOS application. There is a certain reticence (and lack of coders) to make LibreOffice more OSX-like, one of the reasons being put forward is that LibreOffice is provided for multiple OSes and multiple desktop paradigms, which makes deciding on the best course of action hard(er) as there aren't enough Mac coders to be able to develop and support (moving forward) a fully OSX-ified version of LibreOffice. As a result, LO for Mac plays second fiddle to design choices that are made mainly with the Linux desktop environments in mind, unless of course you happen to also have Windows, for which LO generally shows better system integration (more developers being paid through support contracts to sort out issues on Windows machines).
The issue of startup window placement and subsequent document opening window dimensions is known from bug 75644.
*** This bug has been marked as a duplicate of bug 75644 ***