Although this is a smart piece of coding, I would never use it.
This presumptuous behaviour is exactly why I stopped using FaceBook’s mobile site – it’s so heavy on JS that it causes my iPhone 3G to lag, freeze, and crash. But because there’s no browser UI available I can’t do anything when it freezes. It makes the entire FB website unusable on my iPhone and means that when FB screws up I have to exit the entire application and start again in a new tab.
Hiding the toolbar on first load is fine, but there should always be a way of accessing it by simply scrolling back up.
We don’t mess with right-click menu’s for usability’s sake, and we shouldn’t mess with expected UI chrome either.
Matt Wilcox
Although this is a smart piece of coding, I would never use it.
This presumptuous behaviour is exactly why I stopped using FaceBook’s mobile site – it’s so heavy on JS that it causes my iPhone 3G to lag, freeze, and crash. But because there’s no browser UI available I can’t do anything when it freezes. It makes the entire FB website unusable on my iPhone and means that when FB screws up I have to exit the entire application and start again in a new tab.
Hiding the toolbar on first load is fine, but there should always be a way of accessing it by simply scrolling back up.
We don’t mess with right-click menu’s for usability’s sake, and we shouldn’t mess with expected UI chrome either.