What I can't figure is why 2D transitions needs to be hardware accelerated to be smooth in mobile Safari.
Neither why their mighty Nitro JavaScript Engine can't handle smoothly a setTimeOut based fade in/Out.
Google Chrome on 8 years old hardware (less powerful than actual iPhone hardware) renders the moving web better.
Safari is a poor mobile browser.