#890: `field-sizing` CSS property

Visit on Github.

Opened Sep 1, 2023

こんにちは TAG-さん!

I'm requesting a TAG review of field-sizing CSS property.

field-sizing CSS property allows web authors to disable a historical special sizing behavior of HTML form controls. Web authors will be able to make form control sizes automatically-growable depending on their contents.

Further details:

  • I have reviewed the TAG's Web Platform Design Principles
  • Relevant time constraints or deadlines: N/A
  • The group where the work on this specification is currently being done: CSSWG
  • The group where standardization of this work is intended to be done (if current group is a community group or other incubation venue): CSSWG
  • Major unresolved issues with or opposition to this specification: Value keywords are not fixed yet.
  • This work is being funded by: Google

We'd prefer the TAG provide feedback as: 💬 leave review feedback as a comment in this issue and @-notify [@tkent-google]

Discussions

Comment by @torgo Oct 11, 2023 (See Github)

@tkent-google we're going to have a look at this - but do you consider this an early review? It looks to us like this is still being discussed and worked on by the working group so it wouldn't be appropriate as a later stage review. Hoping you can clarify.

Comment by @tkent-google Oct 25, 2023 (See Github)

do you consider this an early review?

I intended this was a specification review, not an early review. When I submitted this review request, we already had a CSSWG resolution, and the discussion was not active. The discussion got active after the request, then it got calm again after two CSSWG resolutions.

Discussed Dec 18, 2023 (See Github)

Amy: originally thought we could fast track this but based on Lea/Sangwhan discussion in slack perhaps not. Need to understand if Lea's thoughts are concerns or not.

we agree it needs Lea to look at it

Comment by @rhiaro Dec 20, 2023 (See Github)

We're really happy to see this important use case being addressed.

We have concerns about the design, and the additional complexity this brings to the mental model for sizing in CSS, but we understand that alternatives have been explored extensively by the WG. Can you please add alternatives considered, and reasons why those designs weren't chosen, to the explainer, so we have this on record for the future?

Thanks!

Comment by @tkent-google Jan 9, 2024 (See Github)

Thank you for the suggestion.

Can you please add alternatives considered, and reasons why those designs weren't chosen

I added a section: https://github.com/tkent-google/explainers/blob/main/form-sizing.md#considered-alternatives

Discussed Feb 5, 2024 (See Github)

Matthew: Considered alternatives were added to the Explainer, as requested.

Amy: proposed closed in December, will just check with Lea

Lea: we discussed this... adding new keywords.. won't be able to apply other keywords to a form control. Fair enough, I'm convinced.

closed

Comment by @rhiaro Feb 5, 2024 (See Github)

Thanks for the extra information, that was very helpful, we're happy to conclude this review.