Comment on A single tweet page is 2.0 MBparentComments−marknutter14yThey'll move to pushState and all will be well. Hash-bang URLs were just a necessary stopgap solutions until more browsers supported pushState.−TazeTSchnitzel14yI would like to think so, but they haven't yet. They don't even load any page content, so that you don't get URLs like http://twitter.com/stuff/1234/things#!/different/stuff−icebraining14yNo version of IE - not even IE9 - supports pushState. Nor does the Android browser, for that matter.http://caniuse.com/history−lparry14yToo bad for IE users. They've said they're redoing it to given users of modern browsers the best experience, and if you use a crap browser you just get full page loads. /#!'s are getting kicked to the curb−udp14yIt's easy enough to use pushState where available and fall back on #!−jonursenbach14yOr just failover to full page refreshes, like we do at gdgt.−TazeTSchnitzel14yNot strictly true. IE10 supports it.−pstjean14yIf you would like to think so, let me give you a reason to do so: http://www.2ality.com/2012/02/twitter-pushstate.html
Comments
They'll move to pushState and all will be well. Hash-bang URLs were just a necessary stopgap solutions until more browsers supported pushState.
I would like to think so, but they haven't yet. They don't even load any page content, so that you don't get URLs like http://twitter.com/stuff/1234/things#!/different/stuff
No version of IE - not even IE9 - supports pushState. Nor does the Android browser, for that matter.
http://caniuse.com/history
Too bad for IE users. They've said they're redoing it to given users of modern browsers the best experience, and if you use a crap browser you just get full page loads. /#!'s are getting kicked to the curb
It's easy enough to use pushState where available and fall back on #!
Or just failover to full page refreshes, like we do at gdgt.
Not strictly true. IE10 supports it.
If you would like to think so, let me give you a reason to do so: http://www.2ality.com/2012/02/twitter-pushstate.html