Web Platform Rules

Interaction and layout

Keep URLs meaningful and navigable through go_router.
Test direct loading of nested routes, refresh, browser back/forward, and history restoration.
Do not intercept browser-reserved keyboard shortcuts.
Ensure hover interactions have keyboard and touch alternatives.
Constrain content width on large monitors.
Test browser zoom, narrow viewports, and text scaling.
Do not display native desktop window title-bar UI merely because the browser viewport is wide.

Handle downloads, clipboard access, and file selection according to browser permissions and supported APIs.
Treat denied permissions, blocked pop-ups, unsupported APIs, and cancelled file selection as recoverable states.
Use browser-safe platform adapters rather than assuming native filesystem access.
Preserve route state in URLs and avoid storing navigational truth only in memory.

Configure hosted fallback behavior so direct nested URLs load correctly.
Test supported browsers and the production build, not only the development server.
Verify browser security policies, asset paths, service-worker behavior if used, and cache invalidation.
Test browser zoom, refresh, direct URLs, history, downloads, clipboard, and file selection.

Load every primary route directly in a new browser tab.
Refresh nested routes and verify the expected screen remains addressable.
Use browser back and forward controls.
Test keyboard, mouse, touch, zoom, and narrow viewport behavior.
Cancel and deny file, clipboard, and download actions and verify recoverable feedback.