[css-forms-1] Text input pseudo definitions too entangled with HTML

[fantasai]

The Form Controls spec defines the ::field-text and ::placeholder pseudo-elements twice, once for <input> and once for <textarea>. They should just be defined once, generically, and the HTML hookup should be an example, similar to how the slider-like controls are defined.

(Try to think of the spec as being written for "generic markup language", with HTML as the primary example, rather than as being written as part of the HTML spec.)

[fantasai]

Relatedly, do we really need ::field-text for <textarea>...?

[josepharhar]

Relatedly, do we really need ::field-text for <textarea>...?

Since the textarea element supports the placeholder attribute just like the input element, I don't see why they shouldn't have the same pseudo-elements.

Whether ::field-text is needed for either element is probably worth justifying.

[fantasai]

@josepharhar I think if we have ::field-text for some form controls that look like text fields, we should have it for all of them. It's an even stronger argument than consistency between single-line inputs and multiline inputs, which behave differently in a number of ways. :)

Anyway, I think this issue should focus on the editorial question and maybe I should push off the ::field-text applicability question to a new issue...

[lukewarlow]

While I understand the reasoning for "generic markup" targeting, the reality is that CSS is largely used with HTML and that is what the primary motivator for all of this is. I think it helps to think in concrete terms while we're still deciding the specifics. Then we can do the editorial run through for stuff like this?

That being said I think we should avoid duplication if possible. So combining textarea with text input seems fine.