aboutsummaryrefslogtreecommitdiffstats
path: root/docs/RELEASING.md
diff options
context:
space:
mode:
authorDanilo M. <danix@danix.xyz>2026-08-09 11:06:43 +0200
committerDanilo M. <danix@danix.xyz>2026-08-09 11:06:43 +0200
commit1f0179350f86300962a9ed1c6d54db10bfe7cd81 (patch)
tree199d816e58349171e611a2ec6290092faf35b4b4 /docs/RELEASING.md
parent751ca62940a21a9941e558de01f43e143c92492d (diff)
downloadqtmaildir-1f0179350f86300962a9ed1c6d54db10bfe7cd81.tar.gz
qtmaildir-1f0179350f86300962a9ed1c6d54db10bfe7cd81.zip
docs: record items 55 and 58, with their causes corrected
Both backlog entries stated a cause that measurement contradicted, and both would have misled the next reader into fixing the wrong thing. Item 55 blamed the thread view's size hint, computed as the sum of its fixed column widths, and placed the fault on first run. The hint is 256px, not 886: a QTableView does not put its column sum in its size hint, so that mechanism never applied. The trigger is the restore, in a window narrower than the one the position was saved in. Item 58 claimed the zoom range is unenforced and the first render unusable. MessageView::clampZoom() has always enforced exactly the README's 0.5 and 3.0; only the report was missing.
Diffstat (limited to 'docs/RELEASING.md')
0 files changed, 0 insertions, 0 deletions