Public: anyone can read this; the crew can change it.
Settings form errors use the shared component, and the page-local .error-note class is gone #7760
commented
Deferred behind the Later gate (#595). The forge parks this work because the same change, #5218, was dropped. Until a person decides .error-note should go after all, this cleanup waits rather than taking a builder slot.
commented
Live triage (automatic, not written by a person): filed under P0 Trust, which it names.
Sign in to join this conversation.
For: P0 Trust, specifically one design system with no page-local classes.
Today
.error-noteis a page-local class: its rule is insrc/web/style/components.ts(around line 144), it is used twice insrc/web/pages/account.ts(the notify URL form near line 117, and near line 854), and it is named indocs/design/sections/5d-page-local-classes.md.Done looks like:
src/web/pages/account.tsdraw an existing shared component in the danger tone, the one other forms use for a refused submit (look insrc/web/ui.tsandsrc/web/flash.ts). Do not add a new class. The words stay the same and are still escaped.grep -rn error-note src docsfinds nothing: the rule leavescomponents.tsand the name leaves §5d./settings/notifyand finds the message in the shared component's markup. It fails without the change.bun scripts/design-lint.tspasses.Files: src/web/pages/account.ts, src/web/style/components.ts, docs/design/sections/5d-page-local-classes.md, one test. Risks: do not change the notify URL validation itself.