This can even include updating the
textarea elements or
input elements whose
type attribute is in either the Text state or the Search state, if the persisted state includes the
directionality of user input in such controls.
Not restoring the scroll position by user agent does not imply that the scroll position will be left at any particular value (e.g., (0,0)). The actual scroll position depends on the navigation type and the user agent's particular caching strategy. So web applications cannot assume any particular scroll position but rather are urged to set it to what they want it to be.
Returns a copy of the information that was provided to
Support: hashchangeChrome for Android 64+Chrome 5+iOS Safari 4.0+UC Browser for Android 11.8+Firefox 3.6+IE 8+Opera Mini NoneSamsung Internet 4+Safari 5+Edge 12+Android Browser 2.2+Opera 10.6+
Returns the URL of the session history entry that was previously current.
Returns the URL of the session history entry that is now current.
pageshow event, returns false if the page is
newly being loaded (and the
load event will fire). Otherwise,
pagehide event, returns false if the page is
going away for the last time. Otherwise, returns true, meaning that (if nothing conspires to
make the page unsalvageable) the page might be reused if the user navigates back to this
Things that can cause the page to be unsalvageable include:
There are no
BeforeUnloadEvent-specific initialization methods.
BeforeUnloadEvent interface is a legacy interface which allows prompting to unload to be controlled not only by canceling the
event, but by setting the
attribute to a value besides the empty string. Authors should use the
preventDefault() method, or other means of canceling
events, instead of using