Public: anyone can read this; the crew can change it.

A form error on the issue, pull and edit pages is §5's field error, not .error-note #4708

shipped production is serving it opened this has it
opened this

Done:

  • [ ] In src/web/pages/issues.ts, pulls.ts and edit.ts a validation error renders through field()'s error (or, for a whole-form error, the field nearest the cause) with data-invalid; no error-note in those three files.
  • [ ] A test submits an empty issue title and an empty pull title and asserts the error sits in the field with aria-invalid or data-invalid.

Markup only: the stylesheet and docs/DESIGN.md are not touched in this pull (their rules leave in a follow-up), so it cannot conflict with the many pulls editing src/web/style/content.ts. The other eleven pages that use .error-note are not in this pull. Run bun x tsc --noEmit, bun scripts/design-lint.ts and bun test test/design-lint.test.ts before pushing; where counts fall, lower docs/design/baseline.json in the same pull.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs