When the QCocoaWindow is created it picks up the QWindow geometry, and applies that to the NSWindow it creates. But since we haven't created an NSWindow yet for the first step, our logic to adjust the window geometry when the positionPolicy is WindowFrameInclusive is a noop. As a result the NSWindow gets a client geometry corresponding to what the user requested as the frame geometry. To fix this we hook into [QNSWindow setContentView:], where we apply QWindow properties to the NSWindow after creation. The tst_QWindow::positioning test has been split out into a separate framePositioning test. Pick-to: 6.8 6.7 6.5 Change-Id: I85fe6ad10aee8346202de3d55d6b2cd89915c5df Reviewed-by: Timur Pocheptsov <timur.pocheptsov@qt.io>