Deprecated: This feature is no longer recommended. Though some browsers might still support it, it may have already been removed from the relevant web standards, may be in the process of being dropped, or may only be kept for compatibility purposes. Avoid using it, and update existing code if possible; see the compatibility table at the bottom of this page to guide your decision. Be aware that this feature may cease to work at any time.
The legacy PerformanceNavigation.type read-only property returns an unsigned short containing a constant describing how the navigation to this page was done.
Warning: This interface of this property is deprecated in the Navigation Timing Level 2 specification. Please use the PerformanceNavigationTiming interface instead.
An unsigned short.
Possible values are:
Value Constant name Meaning0 TYPE_NAVIGATE The page was accessed by following a link, a bookmark, a form submission, a script, or typing the URL in the address bar. 1 TYPE_RELOAD The page was accessed by clicking the Reload button or via the Location.reload() method. 2 TYPE_BACK_FORWARD The page was accessed by navigating into the history. 255 TYPE_RESERVED Any other way.
Note: Historically, developers tested for a type of "TYPE_BACK_FORWARD" to get an indication of back/forward cache (bfcache) hit rate. This however did not provide any reasons for bfcache blocking, or any other data. The PerformanceNavigationTiming.notRestoredReasons property should be used to monitor the bfcache, going forward. See Monitoring bfcache blocking reasons for more information.
PerformanceNavigation interface it belongs to.RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4