diff --git a/source b/source index 3d06f5df9e9..3bdc8f5e99e 100644 --- a/source +++ b/source @@ -95750,8 +95750,8 @@ interface BeforeUnloadEvent : Event { data-x="session-history-traversal-parallel-queue-sync-nav-steps">Synchronous navigation steps are tagged in the algorithm set to allow - them to conditionally "jump the queue". This is handled within apply the history step.

+ them to conditionally "jump the queue". This is handled within apply the history step.

Imagine the joint session history depicted by this Jake diagram:

@@ -99323,8 +99323,7 @@ location.href = '#foo'; data-x="tn-current-session-history-step">current session history step.

  • Return the result of applying the history - step step to traversable given false, false, null, null, and - null.

    • + step step to traversable given false, null, null, and null.

    To apply the push/replace history step given a non-negative integer step @@ -99332,8 +99331,7 @@ location.href = '#foo';

    1. Return the result of applying the history - step step to traversable given false, false, null, null, and - null.

      2. + step step to traversable given false, null, null, and null.

    Apply the push/replace history step never passes source @@ -99341,16 +99339,15 @@ location.href = '#foo'; step. This is because those checks are done earlier in the navigation algorithm.

    -

    To apply the reload history step given a non-negative integer step to a - traversable navigable traversable:

    +

    To apply the reload history step to a traversable navigable + traversable:

    1. Let step be traversable's current session history step.

    2. Return the result of applying the history - step step to traversable given true, false, null, null, and - null.

      3. + step step to traversable given true, null, null, and null.

    Apply the reload history step never passes source snapshot @@ -99365,7 +99362,7 @@ location.href = '#foo';

    1. Return the result of applying the history - step step to traversable given true, true, + step step to traversable given true, sourceSnapshotParams, initiatorToCheck, and userInvolvement.

    @@ -99376,13 +99373,12 @@ location.href = '#foo';

    To apply the history step given a non-negative integer step to a traversable navigable - traversable, with booleans checkForCancelation and - fireNavigateEventOnCommit, source snapshot params-or-null - sourceSnapshotParams, navigable-or-null initiatorToCheck, and - user navigation involvement-or-null userInvolvementForNavigateEvents, - perform the following steps. They return "initiator-disallowed", "canceled-by-beforeunload", "canceled-by-navigate", or - "applied".

    + traversable, with boolean checkForCancelation, source snapshot + params-or-null sourceSnapshotParams, navigable-or-null + initiatorToCheck, and user navigation involvement-or-null + userInvolvementForNavigateEvents, perform the following steps. They return "initiator-disallowed", "canceled-by-beforeunload", "canceled-by-navigate", or "applied".

    1. Assert: This is running within traversable's

    -

  • If navigable is not traversable, and targetEntry is - not navigable's current session history - entry, and targetEntry's document - state's origin is the same as navigable's current session history entry's document state's

    If navigable is not + traversable, and targetEntry is not navigable's current session history entry, and + targetEntry's document state's origin is the same as + navigable's current session history + entry's document state's origin, then fire a traverse navigate event given targetEntry and userInvolvementForNavigateEvents.