Friday, May 10, 2024
 Popular · Latest · Hot · Upcoming
77
rated 0 times [  84] [ 7]  / answers: 1 / hits: 16204  / 13 Years ago, thu, december 8, 2011, 12:00:00

Safari and Chrome (and, I'm guessing, all Webkit browsers) do not respond to window.history.state which is specified in the evolving HTML5 standard here and is implemented in Firefox.



Is there a workaround to read it? Perhaps it is possible to trigger a popstate event in code and return the state from the event handler?


More From » html

 Answers
20

window.history.state is not implemented in webkit broswers currently. There is a request for it, but no steps towards implementation were done so far.



There is a project called history.js which is aiming to provide cross-compatible history management experience.




History.js gracefully supports the HTML5 History/State APIs (pushState, replaceState, onPopState) in all browsers. Including continued support for data, titles, replaceState. Supports jQuery, MooTools and Prototype. For HTML5 browsers this means that you can modify the URL directly, without needing to use hashes anymore. For HTML4 browsers it will revert back to using the old onhashchange functionality.




From that project, History.getState() seems to do what is requested.


[#88654] Thursday, December 8, 2011, 13 Years  [reply] [flag answer]
Only authorized users can answer the question. Please sign in first, or register a free account.
austynp

Total Points: 505
Total Questions: 118
Total Answers: 106

Location: Tajikistan
Member since Sun, Aug 29, 2021
3 Years ago
austynp questions
;