- From: DavidMulder0 via GitHub <sysbot+gh@w3.org>
- Date: Tue, 19 Nov 2024 15:00:11 +0000
- To: public-css-archive@w3.org
Perspective from a developer: We have a nice form abstraction solution, that supports a variety of types extending from the `input[type]`s and renders as the corresponding `input`. Now we hit this intentional 'restriction'. The problem? Switching to textarea is non-trivial (and causes a loss of functionality for non-JS users), as textarea doesn't support different `[type]`s, so one then needs to switch from using semantically correct input[type=email] for example to `textarea[inputmode=email]`... and prevent line breaks using code and rewrite the client-side validation to code, as `textarea` doesn't support `[pattern]`. I am frankly surprised that this isn't a more common problem. Consider this a voice in favor of allowing developers to turn on text wrapping on inputs. -- GitHub Notification of comment by DavidMulder0 Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10019#issuecomment-2485955478 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 19 November 2024 15:00:12 UTC