@videojs/react 10.0.0-rc.2 → 10.0.0-rc.3

package/dist/dev/utils/types.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"types.d.ts","names":[],"sources":["../../../src/utils/types.ts"],"mappings":";;;KAGY,UAAU,WAAW,MAAM,eAAe;EACpD,MAAM,MAAM,IAAI;;;KAIN,eAAe,OAAO,UAAU,OAAO,OAAO,OAAO,UAAU;;KAG/D,WAAW,SAAS,eAAe,eAAe,WAAW;;;;;;;KAQ7D,iBAAiB,sBAAsB,MAAM,IAAI,mBAAmB,SAAS,KACvF,MAAM,IAAI,kBAAkB;;EAI5B,uBAAuB,OAAO;;EAE9B,QAAQ,kBAAkB,OAAO,UAAU;;EAE3C,SAAS,WAAW"}

package/dist/dev/utils/use-attach-iframe.js

@@ -1,13 +0,0 @@
-import { useCallback } from "react";
-//#region src/utils/use-attach-iframe.ts
-function useAttachIframe(media) {
-	return useCallback((element) => {
-		if (element) media.attach?.(element);
-		else media.detach?.();
-		return () => media.detach?.();
-	}, [media]);
-}
-//#endregion
-export { useAttachIframe };
-
-//# sourceMappingURL=use-attach-iframe.js.map

package/dist/dev/utils/use-attach-iframe.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"use-attach-iframe.js","names":[],"sources":["../../../src/utils/use-attach-iframe.ts"],"sourcesContent":["import type { EngineAdapter } from '@videojs/media';\nimport type { RefCallback } from 'react';\nimport { useCallback } from 'react';\n\nexport function useAttachIframe<T extends HTMLIFrameElement>(media: EngineAdapter): RefCallback<T> {\n  return useCallback(\n    (element: T | null) => {\n      if (element) media.attach?.(element);\n      else media.detach?.();\n\n      return () => media.detach?.();\n    },\n    [media]\n  );\n}\n"],"mappings":";;AAIA,SAAgB,gBAA6C,OAAsC;CACjG,OAAO,aACJ,YAAsB;EACrB,IAAI,SAAS,MAAM,SAAS,OAAO;OAC9B,MAAM,SAAS;EAEpB,aAAa,MAAM,SAAS;CAC9B,GACA,CAAC,KAAK,CACR;AACF"}

package/dist/dev/utils/use-attach-media.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"use-attach-media.d.ts","names":[],"sources":["../../../src/utils/use-attach-media.ts"],"mappings":";;;;;;;;iBASgB,eAAe,UAAU,kBAAkB,OAAO,gBAAgB,YAAY"}

package/dist/dev/utils/use-composed-refs.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"use-composed-refs.d.ts","names":[],"sources":["../../../src/utils/use-composed-refs.ts"],"mappings":";;KAIK,YAAY,KAAK,IAAI;;;;;;;;;;iBA0BV,YAAY,MAAM,OAAO,YAAY,KAAK,YAAY,UAAU,YAAY;;;;;;;;;;;;;;iBAqC5E,gBAAgB,MAAM,MAAM,YAAY,OAAO,YAAY"}

package/dist/dev/utils/use-destroy.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"use-destroy.d.ts","names":[],"sources":["../../../src/utils/use-destroy.ts"],"mappings":";UAIU;EACR;;;;;;;;;;;;;;iBAec,WAAW,UAAU,aAAa,oBAAoB"}

package/dist/dev/utils/use-latest-ref.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"use-latest-ref.d.ts","names":[],"sources":["../../../src/utils/use-latest-ref.ts"],"mappings":";;;;;;;;;iBAUgB,aAAa,OAAO,OAAO,QAAQ;EAAW,SAAS;;kBAOtD;OACH,OAAO,SAAS;IAAW,SAAS"}

package/dist/dev/utils/use-media-extension.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"use-media-extension.d.ts","names":[],"sources":["../../../src/utils/use-media-extension.ts"],"mappings":";;;;;;;;;;;iBAegB,kBAAkB,kBAAkB;EAAmB;GACrE,0BAA0B,YACzB"}

package/dist/dev/utils/use-media-instance.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"use-media-instance.d.ts","names":[],"sources":["../../../src/utils/use-media-instance.ts"],"mappings":";;;;;;;;;;;;;;;iBAmBgB,iBAAiB,iBAAiB;EAAU;GAC1D,sBAAsB,UACtB,SAAS,OAAO,oBACf"}

package/dist/dev/utils/use-render.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"use-render.d.ts","names":[],"sources":["../../../src/utils/use-render.tsx"],"mappings":";;;;KAeK,yBAAyB,MAAM,IAAI;UAEvB,wBAAwB;EACvC,uBAAuB,OAAO;EAC9B,QAAQ,kBAAkB,OAAO,UAAU;EAC3C,SAAS,WAAW;;UAGL,oBAAoB,OAAO,4BAA4B;EACtE,OAAO;EACP,MAAM,IAAI,uBAAuB,IAAI;EACrC;EACA,eAAe,aAAa;;;;;;;;;;;;;;;;;;;iBA4Cd,cACd,sBACA,4BAA4B,SAC5B,gBAAgB,kBAEhB,SAAS,SACT,gBAAgB,wBAAwB,QACxC,QAAQ,oBAAoB,OAAO,uBAClC;kBAoDc;OACH,eAAe,SAAS,wBAAwB;OAChD,WAAW,OAAO,4BAA4B,WAAW,oBAAoB,OAAO"}

package/docs/concepts/accessibility.md

@@ -1,68 +0,0 @@
-# Accessibility
-
-How Video.js approaches accessibility, and what you should consider if you're deeply customizing your player
-
-Video.js is built with accessibility in mind so your player can reach the widest possible audience.
-
-Here are some of the accessibility aspects we consider. You should consider them too if you’re performing deeper customization.
-
-## Standards we target
-
-*   [**WAI-ARIA 1.2**](https://www.w3.org/TR/wai-aria-1.2/) defines roles, states, and properties that [assistive technologies](https://www.w3.org/WAI/people-use-web/tools-techniques/) use to understand controls.
-*   [**WCAG 2.2**](https://www.w3.org/TR/WCAG22/) provides success criteria for perceivable, operable, understandable, and robust web content.
-*   [**CVAA**](https://www.fcc.gov/consumers/guides/21st-century-communications-and-video-accessibility-act-cvaa) is a U.S. federal law requiring closed captioning and accessible controls for video content.
-*   [**ADA**](https://www.ada.gov/) is a U.S. civil rights law that prohibits disability discrimination. Courts increasingly apply it to websites, including video players.
-
-## ARIA roles and labels
-
-Components set ARIA roles and attributes automatically. For example, sliders render with `role="slider"` and value attributes, buttons update their `aria-label` based on player state, and decorative elements like time separators are hidden with `aria-hidden="true"`.
-
-Verify that labels are contextually correct for your content and language. Each component’s reference page documents the attributes it sets.
-
-## Keyboard interaction
-
-All interactive components support keyboard control. For example, buttons activate with Enter and Space, sliders respond to Arrow keys, Home, End, and Page Up/Page Down, and popovers close with Escape. Each component’s reference page lists its full keyboard support. We follow the patterns in the [WAI-ARIA Authoring Practices Guide](https://www.w3.org/WAI/ARIA/apg/).
-
-## Focus management
-
-Interactive elements are focusable when enabled and leave the [tab order](https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes/tabindex) when disabled. Popover triggers link to their popups with `aria-controls` and `aria-expanded`.
-
-The player container is focusable and labeled: it takes `role="group"`, `tabindex="0"`, and an `aria-label` you can override. Keyboard users can tab to the player as a whole, and screen readers announce it as a named group.
-
-## Status announcements
-
-The player announces confirmed state changes through a visually hidden live region (`role="status"`), so screen reader users hear when playback starts or pauses, captions turn on or off, fullscreen, picture-in-picture, playback rate, or volume change, and where a seek lands.
-
-Announcements follow confirmed state from the player store rather than requested changes, so routine time updates never reach the live region. Rapid volume and seek changes are grouped into a single announcement, and the player stays quiet while one of its sliders has focus, since the slider already announces its own value. State the store tracks is covered for you; a custom control that tracks its own state needs its own live region.
-
-## Captions and subtitles
-
-The [text tracks feature](../reference/feature-text-tracks.md) supports captions and subtitles. Closed captions in the U.S. are governed by the [FCC](https://www.fcc.gov/) under the [CVAA](https://www.fcc.gov/consumers/guides/21st-century-communications-and-video-accessibility-act-cvaa), which requires both captioning and viewer control over caption appearance (font, size, color, opacity, and edge style). Non-compliance carries legal risk. The [WebKit Caption Display Settings explainer](https://github.com/WebKit/explainers/tree/main/CaptionDisplaySettings) tracks how browsers are bringing these customization preferences into the web platform natively.
-
-## Color contrast
-
-Skins respond to [`prefers-contrast: more`](https://developer.mozilla.org/en-US/docs/Web/CSS/@media/prefers-contrast) by increasing background opacity on overlays and controls, and to [`prefers-reduced-transparency: reduce`](https://developer.mozilla.org/en-US/docs/Web/CSS/@media/prefers-reduced-transparency) by raising baseline opacity so text stays readable over video.
-
-Video is harder than most UI for contrast because the background is always changing. A control that passes checks over a dark frame can disappear over a bright title card. Automated tools won’t catch this, so test your controls against light, dark, and mixed video content. Custom components should test against [WCAG 1.4.3 (contrast minimum)](https://www.w3.org/WAI/WCAG22/Understanding/contrast-minimum) and [1.4.11 (non-text contrast)](https://www.w3.org/WAI/WCAG22/Understanding/non-text-contrast).
-
-## Touch targets
-
-Controls use rem-based sizing so they scale with the user’s font size preference. All interactive elements set [`touch-action: manipulation`](https://developer.mozilla.org/en-US/docs/Web/CSS/touch-action) to eliminate tap delay on touch devices. Skins use [`pointer: fine` and `pointer: coarse`](https://developer.mozilla.org/en-US/docs/Web/CSS/@media/pointer) to adapt transitions for mouse and touch input.
-
-If you build custom controls, target at least 24x24 CSS pixels per [WCAG 2.5.8 (target size minimum)](https://www.w3.org/WAI/WCAG22/Understanding/target-size-minimum). Larger is better on touch-first surfaces.
-
-## Color scheme
-
-Skins adapt to [`prefers-color-scheme`](https://developer.mozilla.org/en-US/docs/Web/CSS/@media/prefers-color-scheme). Borders, backgrounds, and text colors adjust through CSS custom properties. Custom components can use the same design tokens. See [Skins](./skins.md) for details.
-
-## Reduced motion
-
-Skins respect [`prefers-reduced-motion`](https://developer.mozilla.org/en-US/docs/Web/CSS/@media/prefers-reduced-motion) by simplifying or removing animations and transitions. Follow the same pattern in custom components.
-
-## Test with assistive technology
-
-Automated tools catch markup issues but miss real usability problems. Test your player with a [screen reader](https://www.w3.org/WAI/people-use-web/tools-techniques/) ([VoiceOver](https://support.apple.com/guide/voiceover/welcome/mac) on macOS, [NVDA](https://www.nvaccess.org/about-nvda/) or [JAWS](https://www.freedomscientific.com/products/software/jaws/) on Windows) and keyboard-only navigation. Verify that every control is reachable, operable, and announces its purpose and state. The [WAI “Easy Checks”](https://www.w3.org/WAI/test-evaluate/preliminary/) are a good starting point.
-
-## Further reading
-
-The W3C WAI guides on [making audio and video media accessible](https://www.w3.org/WAI/media/av/) and [accessible media players](https://www.w3.org/WAI/media/av/player/) go deeper on everything covered here.

package/docs/concepts/browser-support.md

@@ -1,45 +0,0 @@
-# Browser support
-
-Browsers and rendering environments supported by Video.js 10
-
-Support starts with an evergreen browser baseline and extends to the rendering environments described below.
-
-## Browser baseline
-
-Video.js 10 currently targets **evergreen browsers**: the latest two stable versions of Chrome, Firefox, Safari, and Edge.
-
-Note
-
-Video.js 10 is in beta. The browser support matrix may expand as we approach GA based on community feedback and usage data.
-
-### Why evergreen?
-
-Video.js 10 builds directly on the web platform: custom elements, CSS custom properties, anchor positioning, and modern JavaScript APIs. Targeting evergreen browsers lets us:
-
-*   **Ship smaller bundles** by avoiding polyfills and transpilation for outdated syntax
-*   **Use platform-native features** like `popover` and anchor positioning instead of JavaScript equivalents
-*   **Keep the core slim** so platform-specific adapters (HTML, React) add only what they need
-
-### Progressive enhancement
-
-When we use a platform feature that hasn’t landed in all supported browsers yet, we provide a fallback. The player works either way; the experience may differ slightly in older browsers. For example, tooltips and popovers use CSS anchor positioning where available and fall back to JavaScript-computed positioning where it isn’t.
-
-## Rendering contexts
-
-### WebViews
-
-A [WebView](https://developer.mozilla.org/en-US/docs/Glossary/WebView) is a browser engine embedded inside a native app. WebViews on iOS (WKWebView) and Android (Android WebView) can behave differently from the full browser; autoplay policies, fullscreen APIs, and hardware acceleration can vary.
-
-Video.js 10 beta targets standard browser environments. If you embed a player inside a native app, test it on each platform and WebView version you support.
-
-### Progressive Web Apps
-
-Installed Progressive Web Apps (PWAs) use the browser engine, but their standalone display mode and platform policies can affect fullscreen, media sessions, and other browser integration. Test playback both in a browser tab and in the installed app.
-
-### Smart TVs and set-top boxes
-
-TV platforms run embedded browsers with limited standards support. Video.js 10’s core is not tied to any specific platform, which makes future TV adapters possible, but TV is not a supported target today.
-
-### Server-side rendering
-
-Video.js components render valid markup on the server. Interactivity — state management, media playback, and event handling — requires the browser and kicks in after hydration.

package/docs/concepts/bundlers.md

@@ -1,43 +0,0 @@
-# Bundlers
-
-Bundler requirements for Video.js package exports, CSS, and wrapper libraries
-
-Before the browser runs your application, a bundler such as Vite combines its imports into files the browser can load. Your bundler must understand the import paths published by Video.js packages.
-
-## Package exports
-
-Each Video.js package has an `exports` field in its `package.json`. This field lists the import paths that applications and libraries can use, such as `@videojs/html/video/player` and `@videojs/react/live-video`.
-
-If an older bundler reports that one of these paths is missing or not exported, upgrade the bundler before adding an alias that bypasses the package’s public API.
-
-## Vite compatibility
-
-Use a current Vite release. Testing confirmed that Vite 5.4.19 can load Video.js JavaScript and CSS package exports. Vite 3.2.8 can load the JavaScript, but it cannot load an exported stylesheet such as `@videojs/html/video/skin.css`.
-
-Packaged HTML skins import their own styles, so an HTML application using `@videojs/html/video/skin` doesn’t need to import `skin.css` separately. The CSS limitation matters only when your application imports that stylesheet directly.
-
-## Externalize Video.js in a wrapper library
-
-You can skip this section when building an application.
-
-If you publish a library that expects its users to install Video.js separately, leave Video.js out of your library’s bundle. Rollup calls a dependency left out of the bundle **external**.
-
-Rollup’s array form matches only the exact package name, so `external: ['@videojs/html']` misses imports such as `@videojs/html/video/player`.
-
-Match the package name and everything below it instead:
-
-rollup.config.js
-
-```
-const videojsPeers = ['@videojs/html'];
-
-export default {
-  external(id) {
-    return videojsPeers.some(
-      (packageName) => id === packageName || id.startsWith(`${packageName}/`)
-    );
-  }
-};
-```
-
-Add every `@videojs/*` package your library imports directly to `videojsPeers` and list it in `peerDependencies`.

package/docs/concepts/features.md

@@ -1,142 +0,0 @@
-# Features
-
-The state and actions each feature adds to the player
-
-Not every player needs to support every use case. To address this, Video.js has a concept of **features** — self-contained units of player functionality. Each one adds state properties and actions to the player. For example, “playback” adds `paused` and `play()`, “volume” adds `volume` and `setVolume()`, and so on.
-
-## Using features
-
-### Feature bundles and presets
-
-You probably don’t want to hand-pick every feature your player needs. A **feature bundle** groups the features needed for a specific use case into a single array.
-
-For example, the `/video` preset configures `VideoPlayer` with `videoFeatures`, which bundles playback, volume, time, fullscreen, and more — everything a general video player needs:
-
-tsx
-
-```
-import { VideoPlayer, Video, VideoSkin } from '@videojs/react/video';
-
-<VideoPlayer>
-  <VideoSkin>
-    <Video src="movie.mp4" />
-  </VideoSkin>
-</VideoPlayer>
-```
-
-Feature bundles are usually paired with specific skins and media elements in a **preset**. To learn more about this, and the available presets, you’ll want to check out the presets guide.
-
-- [Learn more about presets](./presets.md)
-
-### Create a player with individual features
-
-If you’re not using presets, you can create a player that has individual features.
-
-tsx
-
-```
-import { createPlayer, playbackFeature, volumeFeature, timeFeature, controlsFeature } from '@videojs/react';
-
-const { Player } = createPlayer({
-  features: [playbackFeature, volumeFeature, timeFeature, controlsFeature],
-});
-```
-
-### Extending a feature bundle
-
-Since feature bundles are just an array of features under the hood, it doesn’t take much to extend one. For example, if you were using the `/background` preset and wanted a play button on your background video, you might add the playback feature.
-
-tsx
-
-```
-import { createPlayer, playbackFeature } from '@videojs/react';
-import { backgroundFeatures } from '@videojs/react/background';
-
-const { Player } = createPlayer({
-  features: [...backgroundFeatures, playbackFeature],
-});
-```
-
-### Access features in components
-
-You access feature state and actions through [`usePlayer`](../reference/use-player.md):
-
-tsx
-
-```
-// Subscribe to state (re-renders when selected values change)
-const { paused, volume } = usePlayer((s) => ({
-  paused: s.paused,
-  volume: s.volume,
-}));
-
-// Call actions
-const store = usePlayer();
-store.play();
-store.setVolume(0.8);
-```
-
-### Feature selectors
-
-Each feature also has a pre-built selector (e.g. [`selectPlayback`](../reference/feature-playback.md), [`selectVolume`](../reference/feature-volume.md)) that returns just that feature’s state and actions:
-
-tsx
-
-```
-import { selectPlayback, usePlayer } from '@videojs/react';
-
-const playback = usePlayer(selectPlayback);
-playback?.play();
-```
-
-### Checking for feature support
-
-Volume, fullscreen, and picture-in-picture expose availability properties because platform support varies. Volume has two independent properties: `volumeAvailability` for changing the volume level and `mutedAvailability` for toggling mute. For example, iOS Safari allows muting but doesn’t allow programmatic volume control.
-
-Value
-
-Meaning
-
-`'available'`
-
-Ready to use
-
-`'unavailable'`
-
-Could work, not ready yet
-
-`'unsupported'`
-
-Platform can never do this
-
-Components that depend on availability (like [`MuteButton`](../reference/mute-button.md), [`PiPButton`](../reference/pip-button.md), and [`FullscreenButton`](../reference/fullscreen-button.md)) handle the three states for you:
-
-*   **`unsupported`** — the HTML custom element receives the native `hidden` attribute (and `data-hidden`); React buttons return `null`. No CSS needed.
-*   **`unavailable`** — the presentation controls stay hidden while capability detection is unresolved. Cast remains visible but disabled when its API is supported and no device is reachable.
-*   **`disabled` prop** — an available button stays visible and focusable with `aria-disabled="true"` plus `data-disabled` for styling.
-*   **`available`** — fully interactive.
-
-Use `data-disabled` to style the non-interactive state:
-
-css
-
-```
-.pip-button[data-disabled] {
-  opacity: 0.5;
-  cursor: not-allowed;
-}
-```
-
-You can also check availability in JS:
-
-PiPControl.tsx
-
-```
-function PiPControl() {
-  const availability = usePlayer((s) => s.pipAvailability);
-
-  if (availability !== 'available') return null;
-
-  return <PiPButton />;
-}
-```