Repository navigation
UI-FE-051 — Define and Enforce the Supported Browser and Wallet Platform Matrix #623
Description
Problem context
The six approved UI batches define screen compositions, but this cross-cutting implementation boundary is not owned by an existing open focused issue. It must be implemented once and reused across the approved screens.
Technical scope
- Publish minimum browser, mobile WebView, wallet-extension, and wallet-connect support.
- Add capability detection and explicit unsupported states.
- Separate browser support from wallet/network authorization.
Security, architecture, and accessibility constraints
- Follow the approved dark-first brand, foundation, route, capability, and screen authorities.
- Contract receipts and reviewed API projections remain authoritative; never fabricate protocol state.
- Treat API, wallet, route, evidence, documentation, and user content as untrusted.
- Missing, stale, wrong-chain, wrong-release, or denied state must fail closed.
- Meet WCAG 2.2 AA behavior for the affected interaction.
Required tests
- Chromium, Firefox, WebKit, mobile viewport, extension absent, connector absent, and unsupported API tests.
- Keyboard/touch interaction parity.
- Polyfill/bundle regression checks.
Acceptance criteria
- Supported platforms pass the agreed smoke matrix.
- Unsupported capability is detected before mutation.
- No user-agent sniffing grants authority.
- Documentation and CI matrix stay synchronized.
Dependencies
- UI-FE-004 — Build Wallet, Network, and Identity Controls #574
- V2-FE-142 — Build the Wallet Integration Compatibility Matrix #410
- UI-FE-045 — Build Global Not-Found, Retired, Maintenance, and Dependency States #615
- Frontend implementation matrix
Non-goals
- Redesigning approved boards.
- Inventing API or contract authority.
- Bundling unrelated screen compositions.
- Applying
Stellar Wavebefore maintainer activation.
Complexity and points
- Medium — 150 points
Candidate only; activation remains maintainer-controlled.
Activity
Chidi-Dev1 commentedon Oct 15, 2026
@Chidi-Dev1 has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Chidi-Dev1 to this issue.
femiolutayo commentedon Oct 15, 2026
@femiolutayo has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @femiolutayo to this issue.
drips-wave commentedon Oct 15, 2026
Congratulations, @femiolutayo! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on October 22, 2026.
🧑💻 @femiolutayo: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.
Warning
When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.
🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.
🌊 Happy Wave 🌊
drips-wave commentedon Oct 20, 2026
This issue has been completed by @femiolutayo as part of the Stellar Wave Program's 10th Wave 🥳
😎 @femiolutayo: You earned 150 Points for completing this issue! Once the Wave's rewards are finalized, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.
🧑💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.