- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Fri, 09 Nov 2018 22:45:04 +0000
- To: public-css-archive@w3.org
The precise nature of the "slow transition" behavior isn't super-specified (tho Web Animations does some nice work in reifying the transition into an explicit Animation object), but I agree with you that Chrome/Firefox/Safari's behavior is the desirable one. Basically, moving an element in the tree should clear *all* style-related information about it; as far as CSS is concerned, the old element simply evaporated into thin air and a brand new element appeared somewhere else. Thus, just as transitions are canceled when the property they're associated with gets changed *again*, transitions should simply be dropped when their associated element disappears. This is the same behavior you'd get from flickering it to `display:none` and back. Whether a move is *technically* a "remove, then insert" (I think it is for other purposes?), it should be treated the same for transition-canceling purposes. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3309#issuecomment-437518771 using your GitHub account
Received on Friday, 9 November 2018 22:45:05 UTC