An interesting use for
requestAnimationFrame to reduce repaints and reflows during scrolling:
A new Github project to document device “oddities”:
If solutions can’t be found, at least it might be nice to know others are having the same problem… :-)
A good history and update on the issue of responsive images:
Marcel, note the format of the
<picture> element that has been proposed, interesting that we came up with nearly the exact solution as well!
You might also want to review the two existing polyfills that make the new
<picture> element work in browsers that do not support it, there might be something useful for Tactile’s version:
- Scott Jehl’s Picturefill
Even if we don’t use the exact API from Ericcson, there is probably something we could learn from their methods?
A bookmarklet to test CSS performance:
It’s a little difficult to watch, because the page blinks and jumps a lot while the tests are running, and depending on the page size and size of the CSS file it could take a little while, but the results are interesting.
The title of the video is about a new Timeline view in Chrome’s Developer Toolbar, but there is also a great deal of information regarding animation optimization, including the new requestAninationFrame:
I know we have plenty to keep ourselves busy right now, but at some point I think a “Best Practices and Recommendations” document for our clients would be a good idea.
I feel like a lot of our “bugs” (and I think performance issues) come from things that could be at least improved, if not eliminated, with better development practices.
Things like using less HTML, using sprites and data URIs to reduce HTTP Requests, minifying CSS and JS, etc., could really help improve the perception of Tactile: if our sites look or feel sluggish, regardless of the reason, our clients, and their users, are going to blame our product…
Here is a nice starter, does anyone else have anything they’d like to include, so we could start building a document?