[WIP] Add 2D matrix dropdown form inputs

[Copilot]

• Review submission issue I want 2D matrix dropdown form inputs  #656 — contains two separate feature requests
• Run duplicate checks for both wants
• Create wants/18b2eec2-49ad-410f-be86-c20aaac2dfe9.md — "I want 2D matrix dropdown form inputs"
  • Tags: html, forms
  • Related: WHATWG select spec, EN 13402 clothing size standard
  • Discussion: I want 2D matrix dropdown form inputs  #656
• Create wants/bd9677b9-2a64-4f48-ab7f-4e581e7557ff.md — "I want typed numeric input fields with units"
  • Tags: html, forms
  • Related: existing want I want the ability to specify `line-spacing` instead of `line-height` #59 (amount element), WHATWG number input spec, CSS Values spec
  • Discussion: I want 2D matrix dropdown form inputs  #656
• Validate both files with npm run validate-want — both pass
• Update original issue I want 2D matrix dropdown form inputs  #656 body (cleaned narrative, no frontmatter) — blocked by API restriction; needs manual action

[Copilot]

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Adds two new “want” entries based on discussion #656, expanding the site’s catalog of proposed HTML form capabilities.

Changes:

• Add a new want proposing a native “amount”/unit-aware numeric form input.
• Add a new want proposing a native 2D/matrix dropdown input pattern for paired selections.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 4 comments.

File	Description
wants/bd9677b9-2a64-4f48-ab7f-4e581e7557ff.md	New want describing unit-aware numeric input / canonicalized submission.
wants/18b2eec2-49ad-410f-be86-c20aaac2dfe9.md	New want describing a 2D matrix select control for paired options.

[Copilot]

The proposal relies on a “canonical unit for form submission”, but it’s not clearly defined how authors declare that canonical unit (especially when value is omitted) or whether step/value are intended to implicitly define it. Consider adding a sentence that explicitly defines where the canonical unit comes from (e.g., a dedicated attribute) and what happens when no default value is present.

[Copilot]

The proposal relies on a “canonical unit for form submission”, but it’s not clearly defined how authors declare that canonical unit (especially when value is omitted) or whether step/value are intended to implicitly define it. Consider adding a sentence that explicitly defines where the canonical unit comes from (e.g., a dedicated attribute) and what happens when no default value is present.

Suggested change

The browser would parse the unit attached to `value` and `step`, allow the user to type in any compatible unit (e.g., pounds when the canonical unit is kilograms), and submit the value in the canonical form. Compound measurements like `5 ft 10 in` should also be supported for height, distance, and similar fields.

The browser would parse the unit attached to `value` and `step`, allow the user to type in any compatible unit (e.g., pounds when the canonical unit is kilograms), and submit the value in the canonical form. Authors should declare that canonical submission unit with a dedicated attribute such as `unit="kg"` or `unit="cm"`; `value` may use any compatible unit as an initial value, and `step` defines only the stepping granularity in its own unit rather than implicitly choosing the submission unit. If `value` is omitted, the control should still use the declared `unit` as the canonical unit for parsing, validation, and form submission. Compound measurements like `5 ft 10 in` should also be supported for height, distance, and similar fields.

[aarongustafson]

@copilot please address the feedback

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

[Copilot]

The submitter name appears misspelled. The original submission (issue/discussion #656) lists the submitter as “Christoph Päper”, but this frontmatter has “Christoph Paper”. Please correct the submitter field so attribution matches the original submission.

Suggested change

	submitter: Christoph Paper
	submitter: Christoph Päper

[Copilot]

@copilot please address the feedback

Done in 21b8097. Changes made:

• wants/bd9677b9 (typed unit input): Added an explicit unit attribute to declare the canonical submission unit, clarified that value may use any compatible unit as an initial display value, and that step defines granularity without implying the submission unit. The example now shows <input type="amount" unit="kg" value="10 lb" step="0.5 lb">. Also covers the value-omitted case.

• wants/18b2eec2 (2D matrix): Already updated to use <select type="matrix"> with standard <option row col> attributes to avoid any custom-element naming confusion.

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

[Copilot]

This related entry links to an internal want page (https://webwewant.fyi/wants/59/) but marks the type as discussion. In this repo, internal want-to-want links use type: want (e.g., wants/5f24adc28dfea402c3830218.md:11). Please change this entry’s type to want so it’s categorized correctly.