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.
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.
No, there are no other platform APIs this feature will be frequently be used in tandem with.
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.
This is a form control feature and I don't expect security 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.
This feature is debuggable by trying to access the form control element's writing-mode CSS value in DevTools.
Does the feature depend on any code or APIs outside the Chromium open source repository and its open-source dependencies to function?
NoShipping on desktop | 118 |
DevTrial on desktop | 117 |
Shipping on Android | 118 |
DevTrial on Android | 118 |
Shipping on WebView | 118 |
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--
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/d0714fc1-e163-4b87-825c-541d54d31ab0n%40chromium.org.
This could be interesting if existing content by accident has used these properties on their form control, but if Gecko has shipped it, we should just make sure it works the same in Chromium.
LGTM3
/Daniel
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw9H3atqsinHzW%2BwHCpkfrgR7oV5k6mne0YRcHA0Mq8nRQ%40mail.gmail.com.
LGTM2
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscribe@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/d0714fc1-e163-4b87-825c-541d54d31ab0n%40chromium.org.
--
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+unsubscribe@chromium.org.