NEW 282244
[Navigation] Investigate max limit of traversals 
https://bugs.webkit.org/show_bug.cgi?id=282244
Summary [Navigation] Investigate max limit of traversals
Patrick Griffis
Reported 2024-10-29 09:21:18 PDT
It appears Chrome limits this to ~48. Maybe worth matching: <!doctype html> <script src="/resources/testharness.js"></script> <script src="/resources/testharnessreport.js"></script> <script> promise_test(async t => { // Wait for after the load event so that the navigation doesn't get converted // into a replace navigation. await new Promise(resolve => window.onload = () => t.step_timeout(resolve, 0)); let first_key = navigation.currentEntry.key; for (let i = 0; i <= 100; i++) await navigation.navigate("#" + i).committed; assert_not_equals(first_key, navigation.currentEntry.key); await navigation.traverseTo(first_key).committed; // This passes in WebKit, fails in Chrome assert_equals(first_key, navigation.currentEntry.key); }, "Test traversing a long distance"); </script>
Attachments
Add attachment proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1 2024-11-05 08:22:12 PST
<rdar://problem/139285110>
Note You need to log in before you can comment on or make changes to this bug.