- From: Khushal Sagar via GitHub <sysbot+gh@w3.org>
- Date: Tue, 18 Oct 2022 17:52:23 +0000
- To: public-css-archive@w3.org
Summary from offline discussion: It makes sense to abort the transition if per element constraints are broken, i.e., no layout containment or the element allows fragmentation. But detecting if the computed value of tags on all DOM elements has changed (so we now have duplicate tags etc.) adds more computation work. And that work would be to detect a developer bug and abort the transition. So not worth it. **Proposed Resolution**: If constraints on elements participating in a transition become unsatisfied after a transition is running, the transition is aborted. -- GitHub Notification of comment by khushalsagar Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7882#issuecomment-1282787737 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 18 October 2022 17:52:24 UTC