Browser support is an application decision tied to actual users, embedded web views, assistive technology, and release economics. A compatibility badge cannot prove that a workflow works on a low-end phone or with keyboard input. This track begins with a plain case-review submission, then adds optional interaction and export capabilities. It covers feature probes, selective polyfills, a device test matrix, and retirement of older paths after measured adoption.
Topics in this track
- Feature Probes and Functional Fallbacks — Gate enhancements on actual capabilities while preserving a server-owned completion path.
- Polyfill Cost and Target Browser Policy — Choose supported environments, optional code, and fallback behavior without shipping unused weight to everyone.
- Cross-Browser Input and Device Contracts — Test task completion through keyboard, touch, composition, assistive technology, and low-end hardware.
- Capability Rollout and Fallback Retirement — Release optional browser paths gradually and remove old branches only after task-level evidence.
Prerequisite paths
Integration and Verification; Browser Capabilities and Permission Lifecycle.
Neighbor track
Web Component Contracts and Interoperability.
Practice path
Build Project: progressive case export release and check decisions in Web Development: components and compatibility quiz.