#240: burn-after-read submenu padding inconsistent with UI #241

Merged
fen merged 1 commits from fix-240 into dev 2026-09-10 23:00:32 +00:00
Collaborator

Fix attempt 1.

Issue: the burn-after-read "Readable N times" submenu on /new had cramped padding (2px 8px 4px) inconsistent with the rest of the UI.

Cause: #burnrow carries both pw-row and submenu classes; the .protect .pw-row rule (added for #20 password-row rhythm) overrode .submenu standard padding.

Fix: scope the override to .protect .pw-row:not(.submenu) so the burn submenu keeps the standard submenu padding (8px 10px) matching the custom-expiry submenu. Password row rhythm unchanged.

Verified with CDP rendered probe: burn submenu computed padding now 8px 10px, identical to custom-expiry submenu; pwrow unchanged at 2px 8px 4px. go build + go test pass.

Ref #240

Fix attempt 1. Issue: the burn-after-read "Readable N times" submenu on /new had cramped padding (2px 8px 4px) inconsistent with the rest of the UI. Cause: #burnrow carries both pw-row and submenu classes; the .protect .pw-row rule (added for #20 password-row rhythm) overrode .submenu standard padding. Fix: scope the override to .protect .pw-row:not(.submenu) so the burn submenu keeps the standard submenu padding (8px 10px) matching the custom-expiry submenu. Password row rhythm unchanged. Verified with CDP rendered probe: burn submenu computed padding now 8px 10px, identical to custom-expiry submenu; pwrow unchanged at 2px 8px 4px. go build + go test pass. Ref #240
fen added 1 commit 2026-09-10 22:58:28 +00:00
#240: keep submenu padding on burn-after-read row
CI / docker (pull_request) Skipped
CI / test (pull_request) Successful in 43s
f25ed8bc5d
fen merged commit 9c0bd7abb9 into dev 2026-09-10 23:00:32 +00:00
Sign in to join this conversation.