Layout.fillWidth inside plain Row is a silent no-op (status row spacing broken)

vybe commented

2026-05-19 04:12:36 +00:00

Collaborator

Problem

In statusRow (a plain Row from QtQuick, not RowLayout):

Item {
    width: 1; height: 1
    Layout.fillWidth: true
}

Layout.fillWidth is an attached property that only works inside RowLayout, ColumnLayout, or GridLayout. Inside a plain Row it is a silent no-op. The spacer never expands, so the exit-node text is not pushed to the right as intended.

Impact

The status row appears crowded with no visual gap between IP and exit-node text. The intended right-alignment silently fails with no warning or error.

## Problem In `statusRow` (a plain `Row` from QtQuick, not `RowLayout`): ```qml Item { width: 1; height: 1 Layout.fillWidth: true } ``` `Layout.fillWidth` is an attached property that only works inside `RowLayout`, `ColumnLayout`, or `GridLayout`. Inside a plain `Row` it is a silent no-op. The spacer never expands, so the exit-node text is not pushed to the right as intended. ## Impact The status row appears crowded with no visual gap between IP and exit-node text. The intended right-alignment silently fails with no warning or error.

vybe commented

2026-05-19 04:38:03 +00:00

Author

Collaborator

FYI from cross-model audit (claude-sonnet-4-6):

statusRow mixes anchors.left/right with an explicit y: Theme.spacingM. While currently functional, this mixed positioning model (anchor-based horizontal + absolute vertical) is fragile. Any future change of the parent to a RowLayout/ColumnLayout would silently override the y binding.

FYI from cross-model audit (claude-sonnet-4-6): `statusRow` mixes `anchors.left/right` with an explicit `y: Theme.spacingM`. While currently functional, this mixed positioning model (anchor-based horizontal + absolute vertical) is fragile. Any future change of the parent to a `RowLayout`/`ColumnLayout` would silently override the `y` binding.

vybe commented

2026-05-19 04:38:05 +00:00

Author

Collaborator

See also #19 (conflicting anchors.fill + anchors.verticalCenter on peer-list delegate Row).

vybe referenced this issue

2026-05-19 04:38:07 +00:00

Conflicting anchors.fill + anchors.verticalCenter on peer-list delegate Row (runtime warning + undefined layout) #19

vybe referenced this issue

2026-05-19 04:46:05 +00:00

Inverted MouseArea + manual size binding anti-pattern in peer list delegate #32

vybe commented

2026-05-19 04:46:09 +00:00

Author

Collaborator

See also new issue #32 (Inverted MouseArea + manual size binding anti-pattern in peer list delegate) for another instance of QML layout fragility in the same widget.

vybe referenced this issue

2026-05-19 04:57:45 +00:00

Hardcoded popout dimensions vs dynamic content (magic numbers, no implicit sizing) #23

vybe commented

2026-05-19 04:59:37 +00:00

Author

Collaborator

FYI from cross-model audit (claude-sonnet-4-6):

statusRow mixes anchors.left/right with an explicit y: Theme.spacingM. While currently functional, this mixed positioning model (anchor-based horizontal + absolute vertical) is fragile. Any future change of the parent to a RowLayout/ColumnLayout would silently override the y binding.

FYI from cross-model audit (claude-sonnet-4-6): `statusRow` mixes `anchors.left/right` with an explicit `y: Theme.spacingM`. While currently functional, this mixed positioning model (anchor-based horizontal + absolute vertical) is fragile. Any future change of the parent to a `RowLayout`/`ColumnLayout` would silently override the `y` binding.

vybe commented

2026-05-19 05:12:39 +00:00

Author

Collaborator

See also #19, #23, #32 — related QML layout/MouseArea fragility.