summaryrefslogtreecommitdiffstats
path: root/tests/auto/bic/data/QtConcurrent.5.13.0.linux-gcc-amd64.txt
diff options
context:
space:
mode:
authorTor Arne Vestbø <tor.arne.vestbo@qt.io>2024-05-16 13:51:11 +0200
committerTor Arne Vestbø <tor.arne.vestbo@qt.io>2024-05-23 18:55:47 +0200
commit668914649c03d502935c79001baf95ac017ba061 (patch)
treecb5a4c8e7ea09c3e57e9dc381f4a8b2df48aad80 /tests/auto/bic/data/QtConcurrent.5.13.0.linux-gcc-amd64.txt
parentbc1f9837815b3a3058be6a51fd032ba10adf472e (diff)
QFrame: Disable implicit inclusion of safe area margins in contents rectHEADdev
The QFrame::frameRect property is implemented in terms of the QWidget's contentsMargins, and when the QFrame is resized it recalculates the new frame rect by reading the contents rect and then setting the widget's content margins based on the new value. This conflicts with the implicit inclusion of safe area margins in the widget's contents rect, as those implicit margins are then persisted as user-set contents margins. If the safe area margins later change (to 0), the frame will still reflect the old safe area margins. We may find a way to untangle this for QFrame, but in the meantime let's set Qt::WA_ContentsMarginsRespectsSafeArea to false. This avoids the issue above, and also informs child widgets of the QFrame that they themselves need to potentially take the safe area margins into account. Disabling Qt::WA_ContentsMarginsRespectsSafeArea in this manner should not cause any major behavior changes, as a QFrame is typically part of a parent widget that does respect the contents margins, and so the frame will not need to apply any margins of its own once the layout settles down. Task-number: QTBUG-125345 Pick-to: 6.7 Change-Id: I936ff5ec9056d05676560cc7659ba31105fdc224 Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@qt.io>
Diffstat (limited to 'tests/auto/bic/data/QtConcurrent.5.13.0.linux-gcc-amd64.txt')
0 files changed, 0 insertions, 0 deletions