You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
None - browser chrome issues can't be detected nor fixed with JavaScript.
My unconfirmed suspicion: The html5 history API landed in WebKit at some point, and eventually made it to all the forks. Implementors of those forks had no proper way to test their implementation, so are likely not even aware of the addressbar issues, as it requires manual testing to see if the address changes or not. From within JavaScript, the API works fine and does its thing. iOS 4.1 had the same issue (or at least very similar) as Android and the Playbook now have...
The text was updated successfully, but these errors were encountered:
Summary:
Especially mobile browsers don't implement the HTML5 history API properly: The API itself is there, but the chrome doesn't updated properly.
Platforms:
How to reproduce:
Reduced Example:
Interactive test with Browserscope integration: http://jquery.bassistance.de/historytest/
Bug Tracker ticket(s):
Workarounds:
None - browser chrome issues can't be detected nor fixed with JavaScript.
My unconfirmed suspicion: The html5 history API landed in WebKit at some point, and eventually made it to all the forks. Implementors of those forks had no proper way to test their implementation, so are likely not even aware of the addressbar issues, as it requires manual testing to see if the address changes or not. From within JavaScript, the API works fine and does its thing. iOS 4.1 had the same issue (or at least very similar) as Android and the Playbook now have...
The text was updated successfully, but these errors were encountered: