The Kraken has been released, iOS5 will support native position:fixed and overflow:scroll. There seems to be a lot of misinformation about what you can really do with such functionalities and why you’ll still be needing iScroll (or other scroll views). Let’s try to clarify a little.
I was recently experimenting with CSS 3D transforms. Is it possible to build a 3D city with just CSS? Yesterday I’ve posted on twitter about a quick CSS 3D demo, here comes the follow up blog post.
It has been a troubled pregnancy, but iScroll 4 is finally ready for beta testing. Here is a quick overview on the main new features of this stellar new release.
After more than 800 questions, requests and suggestions sent for iScroll I finally decided to open a discussion group so that it will be easier to browse and search through the messages.
Off screen items on iScroll are not cached by the mobile browser, when it comes their turn to appear on screen they need a few moments before being accessible, creating a nasty flickering. Well, there’s an easy trick to force the browser to cache all elements and it’s so simple I regret not having tried it before.
I love jQuery, I use it everyday, you can spot it even on this blog. It’s a life saver in the times of desktop browser discrepancies (yes, I’m talking to you IE), but modern browsers and specifically mobile browsers are good enough not to need any bloated framework on their shoulders. In this post I’m showing you that 90% of the times you are using a framework for nothing.
I finally took the time to fix some nasty bugs that were infesting iScroll. This has been the most important bugs hunting session since v3.0. Hurry up, take it while is hot.
One of the most important features has been finally added to iScroll: please welcome the snap scroll. The scrolling area is subdivided into pages and you may choose to scroll to any page both programmatically and with user swipes. The code has been further optimized so that the new feature doesn’t impact on file size nor performance.
The most requested feature for iScroll was probably the ability to programmatically scroll to an element by #id. v3.5 adds this feature and much more. You can actually scroll to any element from a CSS3 query selector opening the door to hardware accelerated carousels.
Frameworks for mobile platforms are coming out quickly. What was pioneering not more than two months ago is now everybody’s land. In this scenario does it still make sense to develop stand alone scripts like iScroll? Short answer: yes.
This latest update brings even better Android compatibility. If I receive no complains I’d consider this release final, freeze the code and move to the next milestone (3.4).
If you use iScroll or any web app that takes advantage of touch events you’ll sooner or later stumble in an annoying bug: when you swipe over the bottom browser bar the touchend event is not fired and the application freezes. Here I’m trying to explain why this happens and how to fix it.
Android is a bad beast but we’ll tame it. My quest to get full Android compatibility continues and this time we are getting pretty close to it. Once again I need beta testers!
You asked for it and now you have it. v3.3 (beta 1) is my first attempt to port iScroll to Android 1.5. It seems to work, but no hardware acceleration. Is it really worth the effort?