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.
None
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
None
None
https://wpt.fyi/results/css/css-ui/parsing https://wpt.fyi/results/html/rendering/widgets
Shipping on desktop | 122 |
DevTrial on desktop | 119 |
Shipping on Android | 122 |
DevTrial on Android | 119 |
Shipping on WebView | 122 |
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).
NoneLGTM1
Very happy to see this addition.
--
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+...@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.
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.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAGH7WqHpLYxALLLhUgk62S31De5DbtKXkR_fEVWqkX2bkgBVVg%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAM0wra_pL3uRKDc6hNpbtFFn0YmkjXGNQKUzomG_kwSwB510Xw%40mail.gmail.com.