4 ms·
The problem is that Twitter broke links to tweet pages by using the #! URL structure. Now you can't load a tweet page without loading the entire app. That's bad
by aaronpk 15y ago
The problem is that Twitter broke links to tweet pages by using the #! URL structure. Now you can't load a tweet page without loading the entire app. That's bad.
- marknutter 15y agoThey'll move to pushState and all will be well. Hash-bang URLs were just a necessary stopgap solutions until more browsers supported pushState.
- TazeTSchnitzel 15y agoI 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 http://twitter.com/stuff/1234/things#!/different/stuff
- pstjean 15y agoIf you would like to think so, let me give you a reason to do so: http://www.2ality.com/2012/02/twitter-pushstate.html http://www.2ality.com/2012/02/twitter-pushstate.html
- icebraining 15y agoNo version of IE - not even IE9 - supports pushState. Nor does the Android browser, for that matter. http://caniuse.com/history http://caniuse.com/history
- udp 15y agoIt's easy enough to use pushState where available and fall back on #!
- jonursenbach 15y agoOr just failover to full page refreshes, like we do at gdgt.
- lparry 15y agoToo 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
- TazeTSchnitzel 15y agoNot strictly true. IE10 supports it.
- deleted 15y ago[deleted]