1) CSS position: fixed The apple development guidelines for mobile safari web-apps encourage you to stay on one page for all user-interaction. Standalone/Offline mode naturally support this recommendation. However without CSS position fixed, there is no way to keep navigation elements on the view, therefore making it extremely cumbersome to let a user navigate the web-app, by requiring him to scroll to the top everytime he wants to go somewhere else.
2) CSS overflow: scroll The current behavior for this property is to make the container scrollable only with a two-finger scroll motion, that is not smooth/ usable at all. In order to implement things like a drilldown (artist- >album->song) it is required to be able to return to previous columns at the same scroll-position as the user was before descending. This is currently impossible on mobile safari. To both these problems there exist unsatisfactory workarounds, such as using mouse gesture events and using css animations to provide a smoother experience. This is not satisfactory because the behavior is still jerky and hard to control. Webkit has the capability to handle both of these standard css/html behaviors perfectly. Apple purposely took them out of mobile safari webkit for reasons that I cannot fathom. Due to consistent refusal of apple to address these problems, even though they have been voiced since nearly two years now, I'm inclined to attribute this complete and utter failure to adhere to the simplest of web-standards on mobile- safari to malice rather then incompetence. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "iPhoneWebDev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/iphonewebdev?hl=en -~----------~----~----~----~------~----~------~--~---
