KAN-71's custom gesture handlers changed pages only after a completed swipe, producing an abrupt transition. Enable WKWebView's built-in interactive back/forward navigation on iOS and macOS so WebKit owns the gesture and its animation. Remove the custom iOS edge recognizers, macOS event monitor and JavaScript history adapter. Keep the existing vertical scroll limits.
This follow-up deliberately focuses on gesture feel at the requester's direction. Handling asynchronously created Inertia history entries is deferred; WebKit can still skip such entries. Horizontal overscroll is unchanged and remains a follow-up. Android behavior and builds are outside this change's scope.
App version is now 0.2.5, macOS bundle/build 10, and iOS bundle/build 5. Package, Rust, Tauri and Xcode versions agree. AGENTS.md now requires app-version and bundle/build increments for every delivered native change, according to the affected platforms, plus synchronized manifests, release notes and the existing consistency test.
Validation:
11 iOS simulator tests passed, including native gesture configuration, empty history, workspace switching and retained vertical scroll bounds.
215 native tests and 19 Rust tests passed; two existing optional integration tests were skipped.
Real macOS WKWebView tests passed for enabling native gestures, full-page back/forward navigation and empty-history boundaries.
The macOS app smoke test passed, including workspace isolation and absence of the removed custom navigation bridge.
Browser regressions passed for page history, text input, short/long page boundaries, horizontal boards and dialog scrolling.
Version consistency, Clippy, formatting, ESLint and diff checks passed.
Automated tests are approved as sufficient for Review. Physical touch/trackpad gesture feel is for the requester to try; these checks do not claim to validate the deferred asynchronous Inertia-history behavior.
Reuses fix/KAN-71-native-navigation-scroll after merged PR #168, as requested. Base remains main; pulled with --ff-only and fast-forwarded the existing branch to 386b258 before this follow-up. Existing local Xcode scheme changes are excluded.
KAN-71's custom gesture handlers changed pages only after a completed swipe, producing an abrupt transition. Enable WKWebView's built-in interactive back/forward navigation on iOS and macOS so WebKit owns the gesture and its animation. Remove the custom iOS edge recognizers, macOS event monitor and JavaScript history adapter. Keep the existing vertical scroll limits.
This follow-up deliberately focuses on gesture feel at the requester's direction. Handling asynchronously created Inertia history entries is deferred; WebKit can still skip such entries. Horizontal overscroll is unchanged and remains a follow-up. Android behavior and builds are outside this change's scope.
App version is now `0.2.5`, macOS bundle/build `10`, and iOS bundle/build `5`. Package, Rust, Tauri and Xcode versions agree. `AGENTS.md` now requires app-version and bundle/build increments for every delivered native change, according to the affected platforms, plus synchronized manifests, release notes and the existing consistency test.
Validation:
- 11 iOS simulator tests passed, including native gesture configuration, empty history, workspace switching and retained vertical scroll bounds.
- 215 native tests and 19 Rust tests passed; two existing optional integration tests were skipped.
- Real macOS WKWebView tests passed for enabling native gestures, full-page back/forward navigation and empty-history boundaries.
- The macOS app smoke test passed, including workspace isolation and absence of the removed custom navigation bridge.
- Browser regressions passed for page history, text input, short/long page boundaries, horizontal boards and dialog scrolling.
- Version consistency, Clippy, formatting, ESLint and diff checks passed.
Automated tests are approved as sufficient for Review. Physical touch/trackpad gesture feel is for the requester to try; these checks do not claim to validate the deferred asynchronous Inertia-history behavior.
Reuses `fix/KAN-71-native-navigation-scroll` after merged PR #168, as requested. Base remains `main`; pulled with `--ff-only` and fast-forwarded the existing branch to `386b258` before this follow-up. Existing local Xcode scheme changes are excluded.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
KAN-71's custom gesture handlers changed pages only after a completed swipe, producing an abrupt transition. Enable WKWebView's built-in interactive back/forward navigation on iOS and macOS so WebKit owns the gesture and its animation. Remove the custom iOS edge recognizers, macOS event monitor and JavaScript history adapter. Keep the existing vertical scroll limits.
This follow-up deliberately focuses on gesture feel at the requester's direction. Handling asynchronously created Inertia history entries is deferred; WebKit can still skip such entries. Horizontal overscroll is unchanged and remains a follow-up. Android behavior and builds are outside this change's scope.
App version is now
0.2.5, macOS bundle/build10, and iOS bundle/build5. Package, Rust, Tauri and Xcode versions agree.AGENTS.mdnow requires app-version and bundle/build increments for every delivered native change, according to the affected platforms, plus synchronized manifests, release notes and the existing consistency test.Validation:
Automated tests are approved as sufficient for Review. Physical touch/trackpad gesture feel is for the requester to try; these checks do not claim to validate the deferred asynchronous Inertia-history behavior.
Reuses
fix/KAN-71-native-navigation-scrollafter merged PR #168, as requested. Base remainsmain; pulled with--ff-onlyand fast-forwarded the existing branch to386b258before this follow-up. Existing local Xcode scheme changes are excluded.