Browser Support
Brok targets current stable browsers while keeping server-rendered content and native form semantics useful when an enhanced browser API or JavaScript behavior is unavailable.
| Tier | Expectation | Examples |
|---|---|---|
| A — supported | Current stable desktop and mobile browsers receive the complete tested experience. | Chrome, Edge, Firefox, Safari |
| B — functional | Older engines may lose cosmetic motion or advanced positioning, but content and native forms remain usable. | Graceful CSS/API fallback |
| Unsupported | End-of-life browsers without the JavaScript, CSS custom-property, or module baseline are not tested. | Legacy embedded engines |
Progressive enhancement rules
- Native form controls remain the baseline when custom selection behavior is unnecessary.
- Popover positioning, view transitions, and advanced motion are enhancements; content must not depend on animation.
- Dialog, sheet, menu, combobox, drag, and canvas behaviors require their installed Alpine module.
prefers-reduced-motion, keyboard input, touch input, and zoomed layouts are part of supported behavior.
Note
A copied component belongs to your application. If your product supports a narrower or older browser matrix, keep that matrix in application tests and adapt the editable source where necessary.