I'm not sure how long it will take until the HTML PR is merged.
Involving a WebKit people sounds helpful.  I'll try it.

On Thu, Dec 21, 2023 at 1:51 AM Philip Jägenstedt <foo...@chromium.org>
wrote:

> Hi Kent,
>
> I see that https://github.com/whatwg/html/pull/9903 is still open, do you
> expect to be able to land it soon? Given the positive review on
> https://github.com/WebKit/standards-positions/issues/231, perhaps
> requesting review from someone on the WebKit team would be fruitful?
>
> Best regards,
> Philip
>
> On Fri, Dec 15, 2023 at 4:04 PM Mike Taylor <miketa...@chromium.org>
> wrote:
>
>> LGTM1
>>
>> Very happy to see this addition.
>> On 12/15/23 2:23 AM, TAMURA, Kent wrote:
>>
>> Contact emails tk...@chromium.org, ikilpatr...@chromium.org
>>
>> Explainer
>> https://github.com/tkent-google/explainers/blob/main/form-sizing.md
>>
>> Specification https://drafts.csswg.org/css-ui/#field-sizing
>> https://github.com/whatwg/html/pull/9903
>>
>> Design docs
>> https://github.com/tkent-google/explainers/blob/main/form-sizing.md
>>
>> Summary
>>
>> By 'field-sizing' property, web authors can disable fixed default sizes
>> of form controls, and make their size depend on their content. It's very
>> easy to provide automatically-growing text fields.
>>
>>
>> Blink component Blink>Layout
>> <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3ELayout>
>>
>> Search tags css <https://chromestatus.com/features#tags:css>, forms
>> <https://chromestatus.com/features#tags:forms>, field-sizing
>> <https://chromestatus.com/features#tags:field-sizing>
>>
>> TAG review https://github.com/w3ctag/design-reviews/issues/890
>>
>> TAG review status Issues open; Review has never been started for three
>> months.
>>
>> Risks
>>
>>
>> Interoperability and Compatibility
>>
>> None
>>
>>
>> *Gecko*: No signal (
>> https://github.com/mozilla/standards-positions/issues/849)
>>
>> *WebKit*: Positive (
>> https://github.com/WebKit/standards-positions/issues/231)
>>
>> *Web developers*: Positive (
>> https://twitter.com/search?q=(%22form-sizing%22%20OR%20%22field-sizing%22)&src=typed_query&f=live
>> )
>>
>> *Other signals*:
>>
>> WebView application risks
>>
>> Does this intent deprecate or change behavior of existing APIs, such that
>> it has potentially high risk for Android WebView-based applications?
>>
>> None
>>
>>
>> Debuggability
>>
>> None
>>
>>
>> Will this feature be supported on all six Blink platforms (Windows, Mac,
>> Linux, ChromeOS, Android, and Android WebView)? Yes
>>
>> Is this feature fully tested by web-platform-tests
>> <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>
>> ? Yes
>>
>> https://wpt.fyi/results/css/css-ui/parsing
>> https://wpt.fyi/results/html/rendering/widgets
>>
>>
>> Flag name on chrome://flags CssFieldSizing
>>
>> Finch feature name CssFieldSizing
>>
>> Requires code in //chrome? False
>>
>> Tracking bug
>> https://bugs.chromium.org/p/chromium/issues/detail?id=1447058
>>
>> Estimated milestones
>> Shipping on desktop 122
>> DevTrial on desktop 119
>> Shipping on Android 122
>> DevTrial on Android 119
>> Shipping on WebView 122
>>
>> Anticipated spec changes
>>
>> Open questions about a feature may be a source of future web compat or
>> interop issues. Please list open issues (e.g. links to known github issues
>> in the project for the feature specification) whose resolution may
>> introduce web compat/interop risk (e.g., changing to naming or structure of
>> the API in a non-backward-compatible way).
>> None
>>
>> Link to entry on the Chrome Platform Status
>> https://chromestatus.com/feature/5176596826161152
>>
>> Links to previous Intent discussions Intent to prototype:
>> https://groups.google.com/a/chromium.org/g/blink-dev/c/cA-cmgrA_QE/m/6uF_LYq4AAAJ
>>
>> This intent message was generated by Chrome Platform Status
>> <https://chromestatus.com/>.
>>
>> --
>> TAMURA Kent
>> Software Engineer, Google
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "blink-dev" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to blink-dev+unsubscr...@chromium.org.
>> To view this discussion on the web visit
>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAGH7WqGsR44%3DxYXUOiXJLPzgTqPiGrfX8zkmdF_6%3DkkT5NPm7g%40mail.gmail.com
>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAGH7WqGsR44%3DxYXUOiXJLPzgTqPiGrfX8zkmdF_6%3DkkT5NPm7g%40mail.gmail.com?utm_medium=email&utm_source=footer>
>> .
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "blink-dev" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to blink-dev+unsubscr...@chromium.org.
>> To view this discussion on the web visit
>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/9c525c4d-4cdf-4f33-bc6b-0a2eef4e74b1%40chromium.org
>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/9c525c4d-4cdf-4f33-bc6b-0a2eef4e74b1%40chromium.org?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
TAMURA Kent
Software Engineer, Google

-- 
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to blink-dev+unsubscr...@chromium.org.
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAGH7WqHpLYxALLLhUgk62S31De5DbtKXkR_fEVWqkX2bkgBVVg%40mail.gmail.com.

Reply via email to