Thank you Alex for the feedback. Replied to the doc.
In short, I'm supportive of giving more controls to authors, to achieve a
more similar level of the typography as LaTeX. There are multiple ideas how
to do it in a world where multiple implementations exist. I think it will
need further author f
Contact emailsko...@chromium.org
ExplainerNone
Specificationhttps://drafts.csswg.org/css-text-4/#word-boundaries
Design docs
https://docs.google.com/document/d/1QyPza8XS4aaYD-yA1MHYx56Hy7DZuEm9cAH-A6lTu8c/edit?usp=sharing
Summary
Changes the line breaking rules for Japanese to keep natural phr
A couple of questions:
- Should we wait until the PR matures a bit and gets reviewed? WebKit's
position is encouraging, but it'd be an even better signal to be able to
land the PR.
- How can we evaluate the compat risk here?
RE the latter, is there a way to usecount how often the base
Let me just say, with my HTML Standard editor hat on, that I am very
excited for these changes. This area is currently a wasteland of
non-interoperable behavior, broken specifications, and
web-developer-expectations violations. The team has done some amazing work
to figure out a model that works we
Title: Blink bug summary
Blink bug status as of 2023-07-03
Component
Open
Slow Triage
Pri-0/1
⭐
No owner
Oldest
Whole Blink17,798(+173)75,003(+216)925(+40)499(+55)109Jan 2015
Uncategorized3(-10)4(-15)0(-1)0(-1)0
Blink>Accessibility508(+14)1,733(+23)43(-3)50(+2)18Feb 2020
Blink>Animation
LGTM3
On Fri, Jun 30, 2023, 21:47 Stephen Chenney wrote:
> Thanks Mike for looking up github usage. It does indeed do nothing and the
> github refs are all -webkit-highlight: none or initial, which I have to
> assume was also none. We checked many of the http-archive links and they
> were all th
