This property specifies the minimum number of characters in a hyphenated word. When applying the hyphenation, the optimal minimum number of characters in the word, before the hyphen, or after the hyphen can vary by the design of the page, or by the language. This property allows the finer grained control of the hyphenation.
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
No
The new CSS property should be rolled out to the autocomplete functionality.
Does the feature depend on any code or APIs outside the Chromium open source repository and its open-source dependencies to function?
No109
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).
NoContact emails
ko...@chromium.org
Explainer
None
Specification
https://w3c.github.io/csswg-drafts/css-text-4/#propdef-hyphenate-limit-chars
Summary
This property specifies the minimum number of characters in a hyphenated word. When applying the hyphenation, the optimal minimum number of characters in the word, before the hyphen, or after the hyphen can vary by the design of the page, or by the language. This property allows the finer grained control of the hyphenation.
Blink component
Blink>Layout>Inline
TAG review
TAG review status
Not applicable
Risks
Interoperability and Compatibility
WebKit: No signal (https://bugs.webkit.org/show_bug.cgi?id=67786) Shipping the old syntax properties `hyphenate-limit-{before,after}` with the `-webkit-` prefix.
--
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/CAHe_1d%2BS7BcxetQpz1%3D%2BWfy%3DV%3DV%3DhOcuT4jZDUZ-8ydLC8zRuQ%40mail.gmail.com.
We could probably take this as a positive signal, despite not being a formal position - there's a WIP patch written by :jfkthame that's been reviewed. But I asked just in case, https://bugzilla.mozilla.org/show_bug.cgi?id=1521723#c9.
Could we request a signal via https://github.com/WebKit/standards-positions/ please? It would be nice if devs didn't have to include this second non-standard property forever.
LGTM2
/Daniel
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/77f16296-80ea-eae1-2c3e-899284238070%40chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/e783a065-1f50-deda-18fe-92f5bee74d67%40gmail.com.