Re: [csswg-drafts] [css-ui] ? Allow <textarea> to be sized by contents. (#7542)

>What are we bikeshedding? Is it the naming of the form-sizing property? A max-content value on another property? If so, which one?

I believe `max-content` was discussed first. Then it was decided on the `form-sizing` property. Some claimed the naming is confusing as long as the values (`auto`/`normal`). Then `max-content` was asked about after, but it that was resolved much earlier to not use make a new property.

(As for bikeshedding, even I'm confused about the naming looking back. `auto` implies recognition of how `auto` used to work, which isn't clear by name only. `normal` is also non specific. Neither describe what is actually happening, just external references.)

>Is this intended to eventually also control <input> width autosizing, which is also a common request (though not equally common)? I really hope we don't introduce two entirely separate bits of syntax for these very similar things.

Discussion came about to how nice it would be to apply this to `<input>` as well. I can understand since authors/designers have to pick which control they want (`<input>` vs `<textarea>`) before presenting to users. Then discussion come about the complexities of making `<input>` multiline. Form submission and keyboard `<Enter>` are points of topic. 

(I'd add the `type=search` and others change the way mobile input methods are also affected and what happens there ("Search button replaces Enter"). Also, on desktop `Shift+Enter` commonly adds a new line in some setups, but would actually submit and open in a new window on `<input>`.)

But if a developer is willing to handle all those UX cases, what would the CSS look like to support making a `<input>` multi-line and sized by contents. Would it match? Would there be more properties? etc

-- 
GitHub Notification of comment by clshortfuse
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7542#issuecomment-1747318142 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 4 October 2023 17:11:47 UTC