Repository navigation
Commit b36db69
committed
Native navigation on iOS: back button and swipe were exiting the site
iOS WebKit's back-trapping heuristic makes the user-facing back
button/swipe skip history entries it deems added without user
interaction - which covers entries the ClientRouter pushes after its
async page fetch. Every in-site navigation got flagged, so one back
gesture vaulted past all of them, out of the site. (Programmatic
history.back() ignores the heuristic, which is why automated checks
passed.)
On iOS/iPadOS, internal links are now marked data-astro-reload so the
router stands down and navigation stays native - correct history by
construction, at the cost of ordinary page loads there. Other platforms
keep client-side routing.
Refs: whatwg/html#7832, WebKit skip logic per Chromium navigation-dev.1 parent f6a8878 commit b36db69
1 file changed
Lines changed: 21 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
53 | 53 | | |
54 | 54 | | |
55 | 55 | | |
| 56 | + | |
| 57 | + | |
| 58 | + | |
| 59 | + | |
| 60 | + | |
| 61 | + | |
| 62 | + | |
| 63 | + | |
| 64 | + | |
| 65 | + | |
| 66 | + | |
| 67 | + | |
| 68 | + | |
| 69 | + | |
| 70 | + | |
| 71 | + | |
| 72 | + | |
| 73 | + | |
| 74 | + | |
| 75 | + | |
| 76 | + | |
56 | 77 | | |
57 | 78 | | |
58 | 79 | | |
| |||
0 commit comments