Re: [csswg-drafts] [css-text-decor-4] Variants of text-decoration-skip-spaces:end behavior, and initial value (#4653)

The CSS Working Group just discussed `Variants of text-decoration-skip-spaces:end behavior, and initial value`.

<details><summary>The full IRC log of that discussion</summary>
&lt;astearns> topic: Variants of text-decoration-skip-spaces:end behavior, and initial value<br>
&lt;astearns> github: https://github.com/w3c/csswg-drafts/issues/4653<br>
&lt;TabAtkins> florian: text-decoration-skip-spaces has a start and end value, meant to make the browser not undelrine spaces at the start and end of the line<br>
&lt;TabAtkins> florian: Spec is specific about what exactly you're supposed to skip<br>
&lt;TabAtkins> florian: In the first approximation it's "all the whitespace"<br>
&lt;TabAtkins> florian: Implemennted in Safari and Firefox, which do differetn from the spec and each other<br>
&lt;TabAtkins> [florian, please fill in these Safari details]<br>
&lt;TabAtkins> florian: In Firefox, it's not only doing (Safari's behavior), it's only skipping them if they're overflowing, not if they fit in the line<br>
&lt;TabAtkins> florian: Possibly they're bugs and need to be fixed, but double-checking that the spec is indeed what we want, given the variants.<br>
&lt;TabAtkins> florian: Also the initial value is different across browsers.<br>
&lt;TabAtkins> florian: Spec says default is "start end"; Level 3 didn't have this as a property but specified it in prose.<br>
&lt;TabAtkins> florian: Chrome behaves as if initi8al value is "none", Safari/Firefox behave as their special variants of "end"<br>
&lt;TabAtkins> florian: So possibly spec is fine and impls are buggy, but if it's intentionally deviating, we should consider that<br>
&lt;TabAtkins> myles: Safari's behavior was implemented before this property existed, I don't think it should influence this.<br>
&lt;TabAtkins> astearns: Action here might just be to file bugs<br>
&lt;myles> s/Safari/WebKit/<br>
&lt;TabAtkins> astearns: And ahve those discussion with implementors<br>
&lt;TabAtkins> astearns: If need be, we can come back to spec changes after<br>
&lt;TabAtkins> fantasai: Yeah, reason to file was just to check that, given the variances, we really wanted the spec behavior.<br>
&lt;TabAtkins> astearns: Any input from Firefox?<br>
&lt;TabAtkins> jkew: I don't currently have an opinion.<br>
&lt;TabAtkins> florian: Okay, so I'll file bugs, assume the spec is good, and we can circle back if there are complaints.<br>
&lt;myles> ScribeNick: myles<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4653#issuecomment-624717409 using your GitHub account

Received on Wednesday, 6 May 2020 15:26:59 UTC