Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
None.| Shipping on desktop | 145 |
| Shipping on Android | 145 |
| Shipping on WebView | 145 |
None.
--
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 visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAGH7WqGKEA45mWLgvTHCX_NEZVyhbA8xUBWV9upboVrBDfRv4g%40mail.gmail.com.
LGTM1Before shipping, can you investigate why https://wpt.fyi/results/css/css-text/text-justify/text-justify-word-separators.html is failing in the same way on all browsers? Is the test broken or is there something missing in the implementation?
On 12/12/25 5:06 a.m., TAMURA, Kent wrote:
On Fri, Dec 12, 2025 at 6:03 PM Philip Jägenstedt <foo...@chromium.org> wrote:
LGTM1
Before shipping, can you investigate why https://wpt.fyi/results/css/css-text/text-justify/text-justify-word-separators.html is failing in the same way on all browsers? Is the test broken or is there something missing in the implementation?
The css-text specification now includes more characters for word separation, and no browsers implement them yet. This also affects the "word-spacing" property, so we'd like to ship it separately.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/87acd44d-2afa-4b8b-a879-661f4873158d%40chromium.org.