Browser Support
Borda targets modern browsers that support ES2020+. The compiled output uses async/await, optional chaining, nullish coalescing, and IntersectionObserver — all available in current versions of major browsers without polyfills.
Supported browsers
| Browser | Minimum version |
|---|---|
| Chrome | 80+ |
| Firefox | 80+ |
| Safari | 14+ |
| Edge | 80+ (Chromium-based) |
| Opera | 67+ |
| Samsung Internet | 13+ |
Required Web APIs
Borda relies on the following browser APIs at runtime:
| API | Used for |
|---|---|
IntersectionObserver | Detecting target element visibility for spotlight positioning |
ResizeObserver | Adapting tooltip and overlay layout when the container resizes |
customElements | Custom Element registration (defineBordaElement()) |
matchMedia | Responsive breakpoint detection |
CSS Custom Properties | Theming and dynamic style overrides |
All listed APIs are supported in the browsers above. If you need to support older browsers, include the corresponding polyfills before loading Borda.
Internet Explorer
Internet Explorer is not supported. Borda uses ES Module syntax, CSS custom properties, and modern DOM APIs that have no IE equivalents.
Mobile browsers
Borda works on mobile Chrome, Safari (iOS), Firefox, and Samsung Internet. The spotlight overlay, tooltip positioning, and keyboard navigation all work on touch devices. Keyboard navigation is optional and can be disabled via tour.hasKeyboardControl: false.
Node.js
For SSR or prerendering scenarios, Borda requires Node.js 16.0 or later. The CommonJS build is available for require() usage. Note that actual tour rendering requires a browser DOM — the Node.js build is intended for server-side mounting logic and config preparation.