-
Notifications
You must be signed in to change notification settings - Fork 3
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Revert "Fenced Frames: Navigations always replace the current entry"
This reverts commit 5e37873045b5e4c8cd4244480476a2b0c23b8114. Reason for revert: Appears to be breaking the tree https://ci.chromium.org/ui/p/chromium/builders/ci/Mac%20Builder%20(dbg)/202959/blamelist Original change's description: > Fenced Frames: Navigations always replace the current entry > > Background: > Fenced frames can navigate themselves but their history is not part of > the browser back/forward list as that could be a communication channel > from the fenced frame to the embedding page. This aligns with MPArch's > disjoint back/forward list for nested frame trees. (For shadowDOM, this > would be achieved with additional API level restrictions like > history.length always returning 1 etc.) > > Current Change: > This CL focuses on fenced frames to always have a replacement-only > navigation which was decided due to being a simpler model since it > doesn't imply that there's a hidden list of back/forward entries for > the nested page, only accessible via history APIs and not via the > back/forward buttons. This is also consistent with the iframes new > opt-in mode for disjoint session history as discussed in > whatwg/html#6501. > This change affects both shadowDOM and MPArch versions. > > Design: > https://docs.google.com/document/d/17rtX55WkxMcfh6ipuhP4mNULIVxUApvYt4ZYXfX2x-s/edit#heading=h.af2cik2j1rbs > > This CL includes browser tests to check the NavigationController's entry > count and > https://chromium-review.googlesource.com/c/chromium/src/+/3227344 > added WPTs for all the history API surface. > > > Bug: 1242533 > Change-Id: Ic574ee1bf87ce3a53dde7d280abaa46233d85b0d > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3216452 > Reviewed-by: Reilly Grant <reillyg@chromium.org> > Reviewed-by: Dave Tapuska <dtapuska@chromium.org> > Reviewed-by: Rakina Zata Amni <rakina@chromium.org> > Reviewed-by: Jeremy Roman <jbroman@chromium.org> > Reviewed-by: Lei Zhang <thestig@chromium.org> > Reviewed-by: Alex Moshchuk <alexmos@chromium.org> > Commit-Queue: Dave Tapuska <dtapuska@chromium.org> > Commit-Queue: Shivani Sharma <shivanisha@chromium.org> > Cr-Commit-Position: refs/heads/main@{#938761} Bug: 1242533 Change-Id: Ib946f629447de53164e1d335cf4b983e1fbdaa35 No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3260236 Auto-Submit: anthonyvd <anthonyvd@chromium.org> Owners-Override: anthonyvd <anthonyvd@chromium.org> Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#938770} NOKEYCHECK=True GitOrigin-RevId: 367479e4b169662f146b1053e9deaeedee035208
- Loading branch information
1 parent
d7bab20
commit 664fff6
Showing
11 changed files
with
9 additions
and
61 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
4 changes: 4 additions & 0 deletions
4
...d_frame/history-length-fenced-navigations-replace-do-not-contribute-to-joint-expected.txt
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,4 @@ | ||
This is a testharness.js-based test. | ||
FAIL All fenced navigations should be replace-only and not contribute to joint session history assert_equals: Navigations inside of a fenced frame are always replacement navigations and never increase `history.length` inside the fence: top-level-fenced-frame expected "PASS > top-level-fenced-frame" but got "FAIL > top-level-fenced-frame history.length: 10" | ||
Harness: the test ran to completion. | ||
|