"Please enter your password." or "Wrong password." error message appears, moving the button down off the screen. The error message space should be reserved so the button doesn't move when the error appears.
This is an obvious violation. Please very carefully audit the codebase for all locations where you insert or update elements like this as a result of user interaction (button clicks, field changes) or API results/errors. Go over each file a few times to determine all places you're modifying the layout intentionally or by accident, and try to itemize them here. Then make a PR fixing all of them.
"Please enter your password." or "Wrong password." error message appears, moving the button down off the screen. The error message space should be reserved so the button doesn't move when the error appears.
This is an obvious violation. Please very carefully audit the codebase for all locations where you insert or update elements like this as a result of user interaction (button clicks, field changes) or API results/errors. Go over each file a few times to determine all places you're modifying the layout intentionally or by accident, and try to itemize them here. Then make a PR fixing all of them.
clawbot
self-assigned this 2026-03-01 01:21:17 +01:00
Audited all JS/HTML files for elements where error/warning/status messages toggle display:none (via hidden class), causing layout shift when they appear or disappear.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
"Please enter your password." or "Wrong password." error message appears, moving the button down off the screen. The error message space should be reserved so the button doesn't move when the error appears.
This is an obvious violation. Please very carefully audit the codebase for all locations where you insert or update elements like this as a result of user interaction (button clicks, field changes) or API results/errors. Go over each file a few times to determine all places you're modifying the layout intentionally or by accident, and try to itemize them here. Then make a PR fixing all of them.
Layout Shift Audit Results
Audited all JS/HTML files for elements where error/warning/status messages toggle
display:none(viahiddenclass), causing layout shift when they appear or disappear.Violations Found (13 total)
confirm-tx-password-errorshowError/hideErrortoggleshiddenclass, defeating existingmin-hconfirm-warningsclassList.add/remove("hidden")confirm-errorsclassList.add/remove("hidden")confirm-feehidden, shown on loadapprove-tx-errorshowError/hideError+ directclassList.add("hidden")approve-sign-errorshowError/hideErrorapprove-sign-danger-warningclassList.add/remove("hidden")export-privkey-flashclassList.add/remove("hidden")delete-wallet-flashclassList.add/remove("hidden")add-wallet-phrase-warningclassList.add/remove("hidden")receive-erc20-warningclassList.add/remove("hidden")add-token-infoclassList.add/remove("hidden")settings-addtoken-infoclassList.add/remove("hidden")Already Correct
send-to-error— usesmin-height: 1.25remwithtextContentswap, nohiddentoggle ✅confirm-recipient-warning— already usesvisibility: hidden/visible✅flash-msg— usestextContentswap withmin-h-[1.25rem], nohiddentoggle ✅Fix Applied
All 13 violations fixed in branch
fix/issue-123-layout-shift-audit:showError/hideErrorin helpers.js now usevisibilityinstead ofhiddenclassstyle="visibility: hidden"+min-heightwhere applicablestyle.visibilityinstead ofclassListfor these elementsdocker build .passes with zero failures