- From: fantasai via GitHub <sysbot+gh@w3.org>
- Date: Wed, 26 Jun 2019 15:43:10 +0000
- To: public-css-archive@w3.org
OK, so we have some possibilities here: - A) Use the "nearest common ancestor" behavior for interpreting `word-break` and `line-break` at element boundaries. This means a given character can be interepreted, effectively, as AL when evaluating whether to break before it and as ID when evaluating whether to break after it. - B) Use per-character classification for interpreting `word-break`; use "nearest common ancestor" for `line-break`. - C) Use per-character classification for interpreting both `word-break` and `line-break`. This will cause some intricate dependencies on the exact way that UAX14 defines line-breaking opportunities, which can result in some oddly asymmetric behavior. Factors to consider: - Implementations are inconsistent in some pretty weird ways, so not helpful. - At least two people have opposite intuitions about this. - We can construct some use cases for A, but don't seem to have any for B or C. - The `white-space` property uses "nearest common ancestor". - I don't like the asymmetric side-effects of definition C (per-character on `line-break`). -- GitHub Notification of comment by fantasai Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3897#issuecomment-505931859 using your GitHub account
Received on Wednesday, 26 June 2019 15:43:11 UTC