Skip to content

Commit

Permalink
Update files/en-us/web/api/navigationactivation/entry/index.md
Browse files Browse the repository at this point in the history
Co-authored-by: Vadim Makeev <[email protected]>
  • Loading branch information
chrisdavidmills and pepelsbey authored Jun 21, 2024
1 parent 1448b86 commit 12f8e2d
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion files/en-us/web/api/navigationactivation/entry/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ browser-compat: api.NavigationActivation.entry

The **`entry`** read-only property of the {{domxref("NavigationActivation")}} interface contains a {{domxref("NavigationHistoryEntry")}} object representing the history entry for the inbound ("to") document in the navigation. This is equivalent to the {{domxref("Navigation.currentEntry")}} property at the moment the inbound document was activated.

There are some cases in which either the from or entry NavigationHistoryEntry objects would not be viable targets for the traverseTo() method, as they might not be retained in history. For example, the Document can be activated using location.replace() or its initial entry could be replaced by history.replaceState(). However, those entries' url property and getState() method are still accessible.
There are some cases in which either the `from` or `entry` {{domxref("NavigationHistoryEntry")}} objects would not be viable targets for the `traverseTo()` method, as they might not be retained in history. For example, the document can be activated using `location.replace()` or its initial entry could be replaced by `history.replaceState()`. However, those entries' `url` property and `getState()` method are still accessible.

## Value

Expand Down

0 comments on commit 12f8e2d

Please sign in to comment.