Thanks for opening this, and for building with Vidstack. Vidstack Player is now in security-only maintenance. Until January 2028, we'll merge priority security fixes into 1.x and nothing else, so we're closing issues that aren't security reports. The teams behind Vidstack, Plyr, Media Chrome, and Video.js now work on [Video.js 10](https://videojs.org?utm_source=vidstack). The migration guide maps Vidstack onto it: [React](https://videojs.org/docs/framework/react/guides/migrate-from-vidstack?utm_source=vidstack) · [Web components and other frameworks](https://videojs.org/docs/framework/html/guides/migrate-from-vidstack?utm_source=vidstack). **Migrating with a coding agent?** Paste the prompt from the guide's AI Quickstart section into your agent: [React](https://videojs.org/docs/framework/react/guides/migrate-from-vidstack?utm_source=vidstack#ai-quickstart) · [Web components and other frameworks](https://videojs.org/docs/framework/html/guides/migrate-from-vidstack?utm_source=vidstack#ai-quickstart). It installs the [Video.js skill](https://github.com/videojs/skills), checks the guide's known gaps against your player before changing code, and plans the installation with `npx @videojs/cli agents init`. If this still matters to you in Video.js 10, open an issue or discussion in [videojs/video.js](https://github.com/videojs/video.js) and link back here so we keep the context. If this is a security vulnerability, don't add details here. Report it privately as described in [SECURITY.md](https://github.com/vidstack/player/blob/main/SECURITY.md).