Contact emailsdizha...@chromium.org

ExplainerNone

Specificationhttps://drafts.csswg.org/css-writing-modes-4/#block-flow

Summary

CSS property writing-mode should be enabled for form controls elements as
it will allow lines of text to be laid out horizontally or vertically. With
this feature, we are allowing the form control elements input, textarea,
select, meter, progress and button to have vertical-rl or vertical-lr
writing mode. This is important for interopability.


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

If a developer set an element to have `writing-mode: vertical-lr`:
Currently, will default to `writing-mode: horizontal-tb` and show the
element as horizontal writing mode. With feature, will have `writing-mode:
vertical-lr` and show the element as vertical writing mode.


*Gecko*: Shipped/Shipping

*WebKit*: In development

*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 property 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 CSS value in DevTools.


Will this feature be supported on all six Blink platforms (Windows, Mac,
Linux, Chrome OS, 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

Flag name on chrome://flagsFormControlsVerticalWritingModeSupport

Finch feature nameFormControlsVerticalWritingModeSupport

Requires code in //chrome?False

Tracking bughttps://bugs.chromium.org/p/chromium/issues/detail?id=681917

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 118. Firefox has
already implemented this feature and Safari is working on it as it is part
of Interop2023.

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 118
DevTrial on desktop 117
Shipping on Android 118
DevTrial on Android 118
Shipping on WebView 118

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).
https://github.com/whatwg/html/issues/8413

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

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%2BSS7eAoSm%2BXfmv1Bnk8CZrMb7xsY7FL3sRgds7-ucUQBaH--g%40mail.gmail.com.

Reply via email to