Bug 282244
| Summary: | [Navigation] Investigate max limit of traversals | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Patrick Griffis <pgriffis> |
| Component: | WebCore Misc. | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | karlcow, webkit-bug-importer |
| Priority: | P2 | Keywords: | BrowserCompat, InRadar |
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Bug Depends on: | |||
| Bug Blocks: | 258384 | ||
Patrick Griffis
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
<rdar://problem/139285110>