Re: [csswg-drafts] [css-text-decor-4] Text Shadow Spread Corners (#7250)

The CSS Working Group just discussed `text shadow spread corners`, and agreed to the following:

* `RESOLVED: Leave text-shadow spread details undefined right now, with possibility of specification later after impl experience.`

<details><summary>The full IRC log of that discussion</summary>
&lt;TabAtkins> Topic: text shadow spread corners<br>
&lt;TabAtkins> github: https://github.com/w3c/csswg-drafts/issues/7250<br>
&lt;TabAtkins> smfr: Issue here is that when you specify spread on a text shadow, the only way UA can implement is by stroking a line with a wider width and shadowing the result.<br>
&lt;TabAtkins> smfr: That has implications for corners and miters<br>
&lt;TabAtkins> smfr: So we need impl experience, need to implement spread on text shadow and see if there are any problems, not sure if there are right now.<br>
&lt;TabAtkins> astearns: I remember we specified increasing the padding of shapes to avoid these kind of spikes<br>
&lt;TabAtkins> astearns: Do you think having a similar algo for shadows might make sense?<br>
&lt;TabAtkins> smfr: Would have to see what that algo is<br>
&lt;TabAtkins> smfr: Concern is that the font might be the one to specify the miter limit, but I don't think it does<br>
&lt;TabAtkins> smfr: If you have a path, maybe the UA can decide the miter limit when drawing the path. Just want confirmation that it's implementable.<br>
&lt;TabAtkins> Without examples of what's up, no opinion here since I don't have enough context.<br>
&lt;TabAtkins> astearns: Anyone with opinions, or people we shoudl tag?<br>
&lt;TabAtkins> fantasai: I'm happy to leave it udnefined, just want to know what to put in the spec.<br>
&lt;TabAtkins> astearns: Lacking opinions, thinkw e should leave it undefined<br>
&lt;TabAtkins> smfr: Might be okay to specify you get rounded corners. If we find it's impossible we can come back to it<br>
&lt;TabAtkins> fantasai: Might be opinions on better ways to do it, looking at miter-limit prop or whatever.<br>
&lt;TabAtkins> fantasai: Think I specced it as rounded corners because, at the time, seemed easiest to implement.<br>
&lt;astearns> shape-margin solution: https://drafts.csswg.org/css-shapes-1/#shape-margin-property<br>
&lt;TabAtkins> astearns: So maybe see if that's an implementable thing for shadows.<br>
&lt;TabAtkins> smfr: Think it might be a little mor ecomplex than that description. Prefer ot have it specified the way impls would do it, which is to stroke a path with a wide stroke width and use that edge to shadow<br>
&lt;TabAtkins> astearns: I think there was an issuea bout shape-margin property too; if there's a better way to specify we can do it in both places<br>
&lt;TabAtkins> astearns: I was trying in that section to be slightly vague to not restrict the particular algo<br>
&lt;TabAtkins> smfr: Briefly playing with it, sometimes in some fonts you'd get a hole due to winding rules.<br>
&lt;TabAtkins> smfr: Reason for impl experience, fonts have weird data.<br>
&lt;TabAtkins> fantasai: So maybe we just make it undefined fo rnow, and can define it with more impl experience<br>
&lt;TabAtkins> smfr: Fine with that.<br>
&lt;TabAtkins> astearns: proposed resolution is to leave it undefined for now, open to specifying it with experience later<br>
&lt;TabAtkins> RESOLVED: Leave text-shadow spread details undefined right now, with possibility of specification later after impl experience.<br>
</details>


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


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 25 May 2022 16:44:02 UTC