- From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
- Date: Tue, 07 Jan 2020 08:40:58 +0000
- To: public-css-archive@w3.org
frivoal has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-text-decor-4] Variants of text-decoration-skip-spaces:end behavior, and initial value == Safari and Firefox both have built-in default behavior that's sort of like `text-decoration-skip-spaces: end`, but not quite the same as [the one specified](https://drafts.csswg.org/css-text-decor-4/#text-decoration-skip-spaces-property), and not quite the same as each other: * Safari skips _all_ preserved U+0020 (but not &nbsp;, or U+3000, or U+2007) on the end side if `white-space` is `pre-wrap`, but not `pre` or `break-spaces` * Firefox skips _overflowing_ preserved U+0020 (but not &nbsp;, or U+3000, or U+2007) on the end side if `white-space` is `pre-wrap`, but not `pre` or `break-spaces` I wonder if we need to make the `end` value (and maybe other values) smarter, or if we need an `auto` of some kind in addition, or if this is just historical accident and all UAs will align on the specified behavior of `end` Also, the spec says that the initial value of `text-decoration-skip-spaces` is `start end`, which is consistent with what level 3 said in prose. However, Chrome behaves as if the initial value was `none`, and Firefox / Safari behave as if the initial value was `magic-end` (see previous point) and don't skip leading spaces at all. Not sure if the spec should align with the browsers or the other way around, but the discrepancy is worth noting. We do have a [resolution in favor of what the spec says](https://lists.w3.org/Archives/Public/www-style/2015May/0314.html), so it's probably just a matter of writing tests and filing bugs… Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4653 using your GitHub account
Received on Tuesday, 7 January 2020 08:41:00 UTC