- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 17 Jul 2024 16:46:33 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-images-4] Gradient interpolation doesn't specify how to handle positionless stops at computed-value time`, and agreed to the following: * `RESOLVED: move the missing position fixup to computed value time` <details><summary>The full IRC log of that discussion</summary> <emilio> TabAtkins: Right now images defines fixup steps to supply default positions and shift stops that are mis-ordered<br> <emilio> ... The second one requires layout-time information<br> <emilio> ... so that step has to happen at used value time<br> <emilio> ... for simplicity at the time I put all the fixups over there<br> <emilio> ... But that means that stops without a position don't have a position at computed value time when interpolating<br> <emilio> ... And there's no reason for doing that, can be done at computed-value time<br> <emilio> ... Proposal is to split the fix-up between computed-value and used-value time fixup<br> <ChrisL> q+ to wonder what the syntax is for the interpolated value<br> <emilio> ... where computed fixup would assign positions<br> <astearns> ack ChrisL<br> <Zakim> ChrisL, you wanted to wonder what the syntax is for the interpolated value<br> <emilio> ... and used would reorder fixups<br> <emilio> ChrisL: what do you actually get?<br> <emilio> TabAtkins: just calc()s<br> <emilio> ... just evenly spacing the missing values<br> <emilio> astearns: So proposal is moving the missing position fixup to computed value time<br> <emilio> q+<br> <astearns> ack emilio<br> <TabAtkins> emilio: my concern is - to be clear, i think every browser does this at used-value time righ tnow<br> <TabAtkins> emilio: this changes the computed value serialization in a somewhat non-trivial way, hope this isn't an issue<br> <ChrisL> q+ to mention missing values and one-stop gradients<br> <TabAtkins> emilio: this is potentially a concern<br> <emilio> TabAtkins: I haven't done a test to see if browsers currently interpolate missing positions or not<br> <emilio> ... I think the gradient interpolation text doesn't take that into account<br> <emilio> ... The serialization one is a meaningful change, we can fix that if it becomes a problem<br> <emilio> emilio: at that point you could just change the interpolation algorithm right?<br> <emilio> TabAtkins: yeah that'd probably be better<br> <astearns> ack ChrisL<br> <Zakim> ChrisL, you wanted to mention missing values and one-stop gradients<br> <emilio> ChrisL: If we're fixing this this, I think a one-stop gradient would go to a 50% rather than 0 or 100%<br> <emilio> TabAtkins: happy to take that up but let's do this resolution first<br> <emilio> RESOLVED: move the missing position fixup to computed value time<br> <ChrisL> OK, the other issue is #10092<br> <ChrisL> https://github.com/w3c/csswg-drafts/issues/10092#issuecomment-2230892477<br> <emilio> emilio: does this _need_ to happen at computed value time? Could be done at parse time right?<br> <emilio> TabAtkins: yeah, but we usually don't do this at parse time<br> <emilio> emilio: yeah just wanted to clarify whether it could be done or I was missing anything<br> <emilio> ChrisL: just wanted to make sure we didn't stomp on the other resolution<br> <emilio> TabAtkins: Yeah it doesn't matter very much<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10374#issuecomment-2233750459 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 17 July 2024 16:46:34 UTC