Everything You Need to Know About the CSS will-change Property
1–10 of 64 posts
Re: Everything You Need to Know About the CSS will-change Property
#2I feel like this is a great example of the... continuing OK-ness of the web as a platform. It feels hacky, but it's considerably less hacky than using unrelated CSS properties, so it's progress and I'm happy with that.
Re: Everything You Need to Know About the CSS will-change Property
#3I feel like this is a great example of the... continuing OK-ness of the web as a platform. It feels hacky, but it's considerably less hacky than using unrelated CSS properties, so it's progress and I'm happy with that.
What would be an example of a non hacky way of hinting to the browser which properties are likely to change?
Re: Everything You Need to Know About the CSS will-change Property
#4I feel like this is a great example of the... continuing OK-ness of the web as a platform. It feels hacky, but it's considerably less hacky than using unrelated CSS properties, so it's progress and I'm happy with that.
What would be an example of a non hacky way of hinting to the browser which properties are likely to change?
In my dream scenario there's no need to do hinting at all. Most other platforms don't require it. But I am living and working in the real world, which has a significant legacy of web technology.
Re: Everything You Need to Know About the CSS will-change Property
#5Small gotcha for people who have been keeping an eye on that from afar for a while: make sure to notice the property is now called "will-change", not "will-animate" anymore.
Re: Everything You Need to Know About the CSS will-change Property
#6I feel like this is a great example of the... continuing OK-ness of the web as a platform. It feels hacky, but it's considerably less hacky than using unrelated CSS properties, so it's progress and I'm happy with that.
What would be an example of a non hacky way of hinting to the browser which properties are likely to change?
Saddling every element in the DOM with a data-will-change="TRUE" or data-might-change="POSSIBLY" and utilizing a heavy jQuery plugin to inject browser-specific CSS rules.
Re: Everything You Need to Know About the CSS will-change Property
#7Earlier quoted context omitted.
What would be an example of a non hacky way of hinting to the browser which properties are likely to change?
In my dream scenario there's no need to do hinting at all. Most other platforms don't require it. But I am living and working in the real world, which has a significant legacy of web technology.
The web doesn't require it either--we've made it this far, after all. I bet every platform has developers who wish they had simple tools to boost performance.
Re: Everything You Need to Know About the CSS will-change Property
#8Earlier quoted context omitted.
In my dream scenario there's no need to do hinting at all. Most other platforms don't require it. But I am living and working in the real world, which has a significant legacy of web technology.
The web doesn't require it either--we've made it this far, after all. I bet every platform has developers who wish they had simple tools to boost performance.
The web doesn't require it either--we've made it this far, after all.
That is a perfect encapsulation of the "OK-ness" he's talking about. Yeah, it works just fine. Yeah, the web doesn't "require" a smart graphics processing engine, it probably didn't "require" videos or the canvas or CSS transitions at all. But "really good" modern platforms have these capabilities, and IMO there's nothing wrong with wanting or trying to push the web to be as good a platform as possible, and it is frustrating (but understandable) that there is so much legacy baggage "holding it back."
Re: Everything You Need to Know About the CSS will-change Property
#9Earlier quoted context omitted.
The web doesn't require it either--we've made it this far, after all. I bet every platform has developers who wish they had simple tools to boost performance.
The web doesn't require it either--we've made it this far, after all. That is a perfect encapsulation of the "OK-ness" he's talking about. Yeah, it works just fine. Yeah, the web doesn't "require" a smart graphics processing engine, it probably didn't "require" videos or the canvas or CSS transitions at all. But "really good" modern platforms have these capabilities, and IMO there's nothing wrong with wanting or tryi…
An important point, however.
One should not assume that all platforms have these capabilities!
Re: Everything You Need to Know About the CSS will-change Property
#10Here's the W3C draft doc on the `will-change` module: http://dev.w3.org/csswg/css-will-change/