- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 25 May 2022 16:35:54 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `composition of inset shadows`. <details><summary>The full IRC log of that discussion</summary> <TabAtkins> Topic: composition of inset shadows<br> <fantasai> astearns: Let's give ppl time to reveiw<br> <TabAtkins> github: https://github.com/w3c/csswg-drafts/issues/7251<br> <TabAtkins> fantasai: I wanted to ask what we should do with inset shadows - what's their stacking order wrt stroke?<br> <TabAtkins> fantasai: Expectation is probably that it's between fill and stroke<br> <TabAtkins> fantasai: But then are we compositing the text decorations with their text before shadowing? If so we can't layer shadows between<br> <TabAtkins> fantasai: You'd ahve to shadow each letter and decoration independently to do that<br> <TabAtkins> smfr: Issue says Chrome and Firefox have somewhat surprising behavior, so [...missed]<br> <TabAtkins> fantasai: Sebastian said "from author's persepctive, expect inset between fill and stroke", but outsets should be below both, so that would require them to be treated differently.<br> <TabAtkins> fantasai: If you have a semi-transparent shadow on text with spread/blur, don't think you'd expect it to be darker where letters are near each other - you'd want them to be shadowed as a whole. That requires compositing text *then* shadowing.<br> <TabAtkins> fantasai: We might not have an answer today, just wanted thoughts on it.<br> <TabAtkins> astearns: If we dont' ahve opinions from the surprising-behavior browsers, do we know who to ask? Is there a Blink engineer we could talk about?<br> <TabAtkins> emilio: What's webkit behavior?<br> <TabAtkins> fantasai: Less interested in current behavior, want to know what we actually want. Changing now isn't going to be a compat question, as we don't have inset shadows yet, and the behavior changes are subtle for outsets anyway (but real)<br> <TabAtkins> fantasai: So question is what authors want, what's possible to implement, and what's the intersection of those two.<br> <TabAtkins> astearns: So I suggest we come up with that definition so impls ahve something to chew on<br> <TabAtkins> astearns: I think you have the outline of possibilities, but not yet a firm decision on what authors would prefer<br> <TabAtkins> fantasai: Right, it's just me and sebastian<br> <TabAtkins> smfr: Is there prior art in InDesign or similar?<br> <TabAtkins> astearns: I could go take a look<br> <TabAtkins> astearns: This is not anything I've looked at before tho, not sure if Photoshop/etc behavior is necessarily what we want. I'll take an action to go look.<br> <TabAtkins> fantasai: Might be interesting to ask people on those teams, who have probably thought about it<br> <TabAtkins> smfr: I'd like to see some more artistic examples rendered with Chrome and Firefox in th eissue, to show the bad behavior more clearly<br> <TabAtkins> astearns: So let's take back to the issue and get more clarity on what we want to specify here.<br> <TabAtkins> astearns: And I'll take an action ot see if I can divine any intent from my company's tooling<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7251#issuecomment-1137524747 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:35:55 UTC