Contact emailsdizha...@chromium.org

ExplainerNone

Specificationhttps://github.com/whatwg/html/issues/8413

Summary

CSS property writing-mode allow elements to go vertical, but users cannot
set the direction in which value changes. With this feature, we are
allowing the form control elements meter, progress and range input type to
have vertical writing mode and choose the form control's value direction.
If direction is rtl, the value is rendered from bottom to top. If direction
is ltr, the value is rendered from top to bottom. For Web compatibility, we
plan to slowly rollout the change in 123 and enable in stable in 124.


Blink componentBlink>Forms
<https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EForms>

TAG reviewNone

TAG review statusNot applicable

Risks


Interoperability and Compatibility

Chrome: implemented behind flag Safari: implemented behind flag Firefox:
implemented for <input type=range> in stable, issue created for
meter/progress.


*Gecko*: No signal

*WebKit*: In development (
https://developer.apple.com/documentation/safari-release-notes/safari-17_4-release-notes)
Added support for vertical writing mode support for form controls.
(12072686)

*Web developers*: No signals

*Other signals*:

Ergonomics

No, there are no other platform APIs this feature will be frequently be
used in tandem with.


Activation

It should not be challenging for developers to take advantage of this
feature immediately as it is simply using the CSS properties on the desired
form control elements.


Security

This is a form control feature and I don't expect security risks.


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?

There are no WebView specific changes with this feature.


Debuggability

This feature is debuggable by trying to access the form control element's
writing-mode and direction CSS values in DevTools.


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-writing-modes/forms?label=master&label=experimental&product=chrome&product=firefox&product=safari&aligned&view=interop&q=label%3Ainterop-2022-forms%20or%20label%3Ainterop-2023-forms


Flag name on chrome://flagsFormControlsVerticalWritingModeDirectionSupport

Finch feature nameFormControlsVerticalWritingModeDirectionSupport

Requires code in //chrome?False

MeasurementNone

Availability expectationFeature is available on Web Platform mainline
within 12 months of launch in Chrome.

Adoption expectationFeature is considered a best practice for some use case
within 12 months of reaching Web Platform baseline.

Adoption planWe plan to release this feature in milestone 124 (Finch in
123). Safari has already implemented this feature.

Non-OSS dependencies

Does the feature depend on any code or APIs outside the Chromium open
source repository and its open-source dependencies to function?
No

Estimated milestones
Shipping on desktop 124
DevTrial on desktop 123
Shipping on Android 124
DevTrial on Android 123
Shipping on WebView 124

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).
HTML spec currently under review: https://github.com/whatwg/html/pull/10096

Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/5082460523331584

This intent message was generated by Chrome Platform Status
<https://chromestatus.com/>.

-- 
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/CA%2BSS7eDti1fFEXgypn%3D3LTdUxikWw6zyTnJS%2BjWtuZStQNKUsA%40mail.gmail.com.

Reply via email to