Re: [w3ctag/design-reviews] Incubation: FormControlRange - Live ranges for <input> and <textarea> (Issue #1142)

csarven left a comment (w3ctag/design-reviews#1142)

The general direction of this design looks good and we also acknowledge that it is addressing a need based on implementation experience with existing approaches.

We appreciate seeing the mention of input types that "do not apply" for `FormControlRange`, which should prevent potentially leaking input length or layout details via `getBoundingClientRect()` or assistive technology APIs. However, the text is confusing: it lists both "Password" (clearly excluded) and "Text", which seems contradictory since `type=text` seems to be a common target for the proposed functionality.

Also appreciate the section on "Unavailable Methods" to avoid exposing or mutating internal nodes, and acknowledging that `FormControlRange` operates in value space.

We would like to encourage you to consider extending [CSS Anchor Positioning](https://www.w3.org/TR/css-anchor-position-1/), as imperative layout with JavaScript isn't great.

We would also like to encourage you to include an "Accessibility considerations" section in the explainer to indicate what was considered (or left out).

Satisfied.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/1142#issuecomment-3360086118
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/1142/3360086118@github.com>