- From: Noam Rosenthal via GitHub <noreply@w3.org>
- Date: Wed, 04 Feb 2026 20:50:34 +0000
- To: public-css-archive@w3.org
> A console warning seems fine... Picking the first one seems a bit easier implementation-wise since you can process as you go, and it matches the way we currently do the check, but I don't have super-strong feelings. > > However that brings the question of what to do with other error conditions... Should we just skip e.g. fragmented elements? That kind of silent failure might be worse... I think this is the kind of error that should be represented in dev-tools (or equivalents), and maybe have an error event or some such if it can help, but try to default to not skipping the transition in either case. -- GitHub Notification of comment by noamr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13438#issuecomment-3849680627 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 4 February 2026 20:50:35 UTC