- From: Jeffrey Yasskin <notifications@github.com>
- Date: Mon, 14 Apr 2025 20:06:30 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 15 April 2025 03:06:34 UTC
jyasskin left a comment (w3ctag/design-reviews#1001) We looked at this in a breakout today, and we agree with Jake that `auto` is not the right keyword for this fallback behavior. We appreciate the CSSWG's attempt to give developers a way to make view transitions that "just work", but it looks like the behavior has more sharp edges than expected. When CSS uses the `auto` keyword, it should generally be safe enough to be the default, and it doesn't look like this is. We don't feel strongly that there _must_ not be a keyword for this behavior, but because this behavior is achievable using `attr(id type(<custom-ident>), match-element)`, we'd encourage the WG and browsers to spend some more time looking for a safer default behavior before giving this behavior a keyword. We're still satisfied with the `match-element` keyword, but switching the Resolution for the `auto` keyword. -- Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/1001#issuecomment-2803634513 You are receiving this because you are subscribed to this thread. Message ID: <w3ctag/design-reviews/issues/1001/2803634513@github.com>
Received on Tuesday, 15 April 2025 03:06:34 UTC