Pages actions reject capacitor:// URLs in the iOS WebView
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 新手友好度
- 68/100
- Issue 类型
- 缺陷
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
- 技术栈
- typescript
- 领域
- frontend
调研方向
Start by locating the Pages navigation engine and its URL scheme guard, then read the same-app URL comparison and related tests. Add coverage for capacitor://localhost navigation and for a different Capacitor host; verify HTTP(S) behavior is unchanged and other schemes remain rejected.
由索引模型根据 Issue 内容生成。
描述
Problem
Void Pages rejects capacitor:// URLs, which Capacitor uses by default for local pages in its iOS WKWebView. Initial rendering and hydration work, but submitting a Pages action fails with:
Void Router: refusing to navigate to a capacitor: URL.
Observed with Void / @void/react 1.1.11 on an iOS 26.1 simulator. The same protocol guard is present on main (9ed64ba).
Reproduction
- Serve a Void React Pages application in a Capacitor iOS WebView at
capacitor://localhost, with page requests forwarded to its Worker. - Hydrate the page and submit a Pages form action, or invoke
router.visit('/users', { method: 'POST' }). - The navigation engine rejects the URL before sending the page request.
Expected: same-app Pages GET/POST navigation works under the default capacitor:// scheme.
Changing server.iosScheme to HTTP(S) is not a workaround: WKWebView already handles those schemes and Capacitor cannot register them. See Capacitor's configuration reference.
Proposed scope
Allow capacitor: alongside HTTP(S) in the Pages navigation engine. It also needs a small same-app URL comparison adjustment: new URL('capacitor://localhost/users').origin is "null", so comparing that value directly with WKWebView's window.location.origin does not identify the local app. Compare protocol and host for capacitor: only, preserving HTTP(S) behavior and rejecting other schemes.
No Capacitor dependency or configurable scheme registry is needed. Different Capacitor hosts must not be treated as the same origin.
- 主要语言
- TypeScript
- 星标
- 402
- 派生
- 32
- 平均合并
- 12 小时 28 分钟
- 30 天内合并 PR
- 77
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
voidzero-dev/void 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 82/100
voidzero-dev/void#478 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
voidzero-dev/void#463 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
voidzero-dev/void#459 ·
维护者通常 1 天内回复
-
bug
难度 1/5 1-3 小时 新手友好度 78/100
voidzero-dev/void#428 ·
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 56/100
voidzero-dev/void#477 ·
维护者通常 1 天内回复
查看 voidzero-dev/void 的全部 Issue
相似的 Issue
-
documentation
难度 2/5 1-3 小时 新手友好度 74/100
components-web-app/docs#260 ·
-
难度 1/5 1 小时以内 新手友好度 65/100
521xueweihan/HelloGitHub#4025 ·
-
难度 2/5 1-3 小时 新手友好度 72/100
-
难度 2/5 1-3 小时 新手友好度 75/100
ctrf-io/playwright-ctrf-json-reporter#117 ·
维护者通常 1 天内回复
-
chore docs good first issue
难度 2/5 1-3 小时 新手友好度 87/100
Karthik-beta/Blinkql#105 ·
维护者通常 1 天内回复