- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Thu, 05 Jul 2018 00:12:37 +0000
- To: public-css-archive@w3.org
The Working Group just discussed `Contain may not want to be animatable`, and agreed to the following: * `RESOLVED: contain is not animatable` * `RESOLVED: will-change is not animatable` <details><summary>The full IRC log of that discussion</summary> <fantasai> Topic: Contain may not want to be animatable<br> <Rossen> github:https://github.com/w3c/csswg-drafts/issues/2737<br> <fantasai> birtles: Since then I spoke to someone working on optimizations that key off contain<br> <fantasai> birtles: He agreed that unless there's a compelling use case to make contain animatable, safest to make it not animatable for now<br> <fantasai> TabAtkins: I'm fine with that<br> <fantasai> florian: Currently discrete, wnat to change to none<br> <fantasai> fantasai: +1 from me<br> <fantasai> dbaron: Does this match display?<br> <fantasai> florian: yeah, that's the point<br> <fantasai> RESOLVED: contain is not animatable<br> <fantasai> ericwilligers: How about will-change?<br> <fantasai> TabAtkins: animating will-change is probably wrong.<br> <fantasai> fantasai: It could impact your internal structures, so probably good to make not animatable<br> <fantasai> birtles: [...]<br> <fantasai> birtles: If your transition has will-change in it, then stacking contexts might change...<br> <fantasai> shane: I agree with your argument<br> <dbaron> s/[...]/spec says that transform animations cause a stacking context during the entire delay phase of the animation; if you apply that to will-change as well.../<br> <dbaron> birtles also mentioned the use case of setting 'will-change' a second before the animation actually starts doing things<br> <fantasai> birtles: We might be able to fix that layer, but for now seems better to make it not animatable for now<br> <fantasai> RESOLVED: will-change is not animatable<br> <TabAtkins> `will-not-change` obvs<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2737#issuecomment-402574750 using your GitHub account
Received on Thursday, 5 July 2018 00:12:39 UTC