LGTM2
/Daniel
On 2022-10-26 18:01, Mike Taylor wrote:
Thanks - LGTM1
On 10/21/22 12:58 PM, Koji Ishii wrote:
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.
Thank you.
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.
Thanks, done here
<https://github.com/WebKit/standards-positions/issues/79>. I chatted
with a WebKit engineer a few months ago, they didn't have an
active plan to update the syntax at that point.
On Sat, Oct 22, 2022 at 12:06 AM Mike Taylor <miketa...@chromium.org>
wrote:
On 10/21/22 3:47 AM, Koji Ishii wrote:
Contact 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
<https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3ELayout%3EInline>
TAG review
TAG review status
Not applicable
Risks
Interoperability and Compatibility
/Gecko/: No signal
(https://bugzilla.mozilla.org/show_bug.cgi?id=1521723)
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.
/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.
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.
/Web developers/: Positive
(https://medium.com/clear-left-thinking/all-you-need-to-know-about-hyphenation-in-css-2baee2d89179#8434)
/Other signals/:
https://justmarkup.com/articles/2019-01-28-a-look-at-css-hyphenation-in-2019/#too-much-hyphenation
https://generatedcontent.org/post/44751461516/finer-grained-control-of-hyphenation-with-css4
https://bugs.chromium.org/p/chromium/issues/detail?id=924069
https://bugzilla.mozilla.org/show_bug.cgi?id=1521723
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?
No
Debuggability
The new CSS property should be rolled out to the
autocomplete functionality.
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
Requires code in //chrome?
False
Tracking bug
https://bugs.chromium.org/p/chromium/issues/detail?id=924069
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
109
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).
No
Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/5150761588097024
Links to previous Intent discussions
Intent to prototype:
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAHe_1d%2BBZ_90HVACwsBEDSBnTB_LDfF%3DriVmi2c%3DzUyMVcDYAw%40mail.gmail.com
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/CAHe_1d%2BS7BcxetQpz1%3D%2BWfy%3DV%3DV%3DhOcuT4jZDUZ-8ydLC8zRuQ%40mail.gmail.com
<https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAHe_1d%2BS7BcxetQpz1%3D%2BWfy%3DV%3DV%3DhOcuT4jZDUZ-8ydLC8zRuQ%40mail.gmail.com?utm_medium=email&utm_source=footer>.
--
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/77f16296-80ea-eae1-2c3e-899284238070%40chromium.org
<https://groups.google.com/a/chromium.org/d/msgid/blink-dev/77f16296-80ea-eae1-2c3e-899284238070%40chromium.org?utm_medium=email&utm_source=footer>.
--
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/e783a065-1f50-deda-18fe-92f5bee74d67%40gmail.com.
