@videojs/react 10.0.0-beta.31 → 10.0.0-beta.32

package/docs/concepts/typescript.md

@@ -0,0 +1,34 @@
+# TypeScript
+
+TypeScript version and module resolution requirements for Video.js packages
+
+Video.js packages require **TypeScript 5.0 or newer**. TypeScript must also follow the import paths that each package publishes.
+
+## TypeScript version
+
+Video.js type files use syntax introduced in TypeScript 5.0. Older versions cannot read that syntax. The `skipLibCheck` option does not help because TypeScript must read a type file before it can skip checking it.
+
+## Module resolution
+
+Video.js packages define their supported import paths using [package exports](./bundlers.md). Most web applications should use the following configuration. It makes TypeScript follow the same package rules as the bundler that builds the application:
+
+tsconfig.json
+
+```
+{
+  "compilerOptions": {
+    "module": "ESNext",
+    "moduleResolution": "bundler"
+  }
+}
+```
+
+If Node.js runs files emitted directly by TypeScript, use `node16` for both `module` and `moduleResolution`, or use `nodenext` for both.
+
+Do not use the older `node` setting, now called `node10`. It does not understand package exports and can report valid Video.js imports or types as missing.
+
+## Errors from other dependencies
+
+The older `node` setting allowed applications to import almost any file inside a dependency. Modern settings allow only the paths that dependency publishes. Changing the setting can therefore reveal an existing import into another package’s private files.
+
+If the error names a package outside `@videojs/*`, update that dependency or use one of its supported import paths. A TypeScript `paths` override can be a temporary bridge when no supported replacement exists. Do not switch back to the older resolver because that also breaks Video.js type resolution.

package/docs/concepts/ui-components.md

@@ -1,14 +1,16 @@
 # UI components
 
-How Video.js UI components work — one element per component, data attributes for state, and compound composition.
+How Video.js UI components use focused elements, data attributes for state, and compound composition.
 
 UI components are controls like buttons, sliders, and time displays.
 
-Every UI component renders exactly one HTML element, taking inspiration from projects like [shadcn/ui](https://ui.shadcn.com/) and [Base UI](https://base-ui.com/). This approach gives you control over styling and behavior while handling the complex interactions for you.
+Visible UI components render at most one HTML element, taking inspiration from projects like [shadcn/ui](https://ui.shadcn.com/) and [Base UI](https://base-ui.com/). This approach gives you control over styling and behavior while handling the complex interactions for you. State-only components render no markup, and controls can skip rendering when their feature is unavailable.
+
+Individual controls provide interaction, accessible names, and state. You add their visible text or icons and CSS. Sliders also need the child elements and styles shown on their reference pages.
 
 ## Where to put your components
 
-UI Components can go anywhere inside a [`<Player>`](../reference/player-provider.md).
+UI components can go anywhere inside a [`<Player>`](../reference/player.md).
 
 However, you should consider placing your components in `<Container>`. Components in `<Container>` will go fullscreen with the player, respond to user activity, and more.
 
@@ -16,6 +18,8 @@ However, you should consider placing your components in `<Container>`. Component
 
 ## Styling and customization
 
+For components you add yourself, use the documented props, state `data-*` attributes, and CSS custom properties. Add your own `className` when you need a selector.
+
 ### The `render` prop
 
 The `render` prop is the primary customization mechanism. It accepts a function that receives `props` and `state`, and returns your element. The `props` object includes event handlers, ARIA attributes, data attributes, and a ref — always spread `{...props}` to keep everything working:
@@ -23,10 +27,13 @@ The `render` prop is the primary customization mechanism. It accepts a function
 tsx
 
 ```
+import { PlayButton } from '@videojs/react';
+import { PauseIcon, PlayIcon } from '@videojs/react/icons';
+
 <PlayButton
   render={(props, state) => (
     <button {...props}>
-      {state.paused ? 'Play' : 'Pause'}
+      {state.paused ? <PlayIcon /> : <PauseIcon />}
     </button>
   )}
 />
@@ -67,7 +74,7 @@ Some components also expose **CSS custom properties** for continuous values like
 
 ## Compound components
 
-Complex interactions are split into composable parts. A parent manages shared state while children consume it. Each part is still one element.
+Complex interactions are split into composable parts. A parent manages shared state while children consume it. Each visible part owns at most one element.
 
 Compound components use dot notation off a shared namespace:
 

package/docs/concepts/why-videojs.md

@@ -4,7 +4,7 @@ The open-source video player for React and HTML. Lightweight, accessible compone
 
 Video.js is the open-source video player for the web. It makes web video easy, performant, accessible, and customizable.
 
-Let’s dig into when you’d want to use Video.js, starting with the the question we hear most…
+Let’s dig into when you’d want to use Video.js, starting with the question we hear most…
 
 ## Why not `<video>`?
 
@@ -28,17 +28,17 @@ Firefox
 
 ### Video interactions
 
-Video often involves a lot more than an MP4 in `src`. Rich playback features (like thumbnail previews, adaptive bitrate, quality selection, chapters, audio track switching, control localization, error UI, live-streaming UI, analytics, ads, 360 video, Chromecast, AirPlay, DRM, and more) are *possible* with the video element but require complex wiring and deep consideration for maintainabilty and [accessibility](./accessibility.md).
+Video often involves more than an MP4 in `src`. Features like thumbnail previews, adaptive bitrate, quality selection, chapters, audio track switching, localized controls, error UI, live-streaming UI, AirPlay, and DRM are *possible* with the video element, but require complex wiring and careful work on maintainability and [accessibility](./accessibility.md).
 
-Video.js aims to handle this all out of the box. (Though some features are still under development. Stay tuned!)
+Video.js provides accessible, composable building blocks for these common playback and streaming features. Other integrations, including ads and emerging media formats, remain under development as version 10 matures.
 
 ### Streaming formats and sources
 
-Behind features like adaptive bitrate and quality selection are video formats like HLS or DASH – videos broken into segments that can be selected according to bandwidth and preferences. Not every browser supports HLS, and DASH support is even more limited. Video.js closes the gap so the same `src` works everywhere.
+Behind features like adaptive bitrate and quality selection are streaming formats such as HLS and DASH. They split video into segments that a playback engine can select based on bandwidth and preferences. Choose the matching Video.js media component to play these formats across browsers while keeping the surrounding player state and UI consistent.
 
-Of course, your video might not be coming from a `src` like that. It might be provided by a service. However, services like YouTube, Vimeo, and Mux each speak their own API. Switching from a self-hosted file to a hosted service shouldn’t mean switching players. Video.js abstracts the source so you can change where the video comes from without rewriting the surrounding code.
+Of course, your video might not be coming from a `src` like that. It might be provided by a service. However, services like YouTube, Vimeo, and Mux each speak their own API. Video.js gives their media components a consistent interface, so changing providers doesn’t require rebuilding the player around them.
 
-Video.js even considers sources like canvas-based MoQ or animated GIFs, all with the same components.
+That boundary also gives us a path to future sources such as canvas-based MoQ playback and use cases such as animated GIF replacement without rebuilding the controls around them.
 
 ## Why Video.js?
 
@@ -68,7 +68,7 @@ Of course, you don’t have to think about every feature you’re going to need
 
 ### Framework-native
 
-Many player libraries wrap a single web component for every framework. That works, until you reach the seams: refs you can’t pass through, state that doesn’t reconcile, prop names that aren’t quite React or HTML. Video.js ships idiomatic APIs in each framework: React components and hooks for React, custom elements and controllers for HTML. (And we plan on supporting more frameworks in the futrue!)
+Many player libraries wrap a single web component for every framework. That works, until you reach the seams: refs you can’t pass through, state that doesn’t reconcile, prop names that aren’t quite React or HTML. Video.js ships idiomatic APIs for its supported frameworks: React components and hooks for React, and custom elements and controllers for HTML.
 
 The player feels like the rest of your app.
 
@@ -78,6 +78,7 @@ HTML
 
 ```
 import { VideoPlayer, Video, VideoSkin } from '@videojs/react/video';
+import '@videojs/react/video/skin.css';
 
 function MyPlayer() {
   return (
@@ -91,7 +92,10 @@ function MyPlayer() {
 ```
 
 ```
-<script type="module" src="@videojs/html/video/player"></script>
+<script type="module">
+  import '@videojs/html/video/player';
+  import '@videojs/html/video/skin';
+</script>
 
 <video-player>
   <video-skin>
@@ -104,6 +108,8 @@ function MyPlayer() {
 
 Most player libraries draw a line between “configurable through props” and “fork the source.” Cross the line and you’re on your own. Video.js lets you eject any skin and walk away with the source: components in your framework’s language that you can read and change. The skin you ship is yours; the rest of the player keeps working underneath it.
 
+We don’t want to cram every possible player into one configuration API. Packaged skins cover common visual changes. For everything else, eject early and compose the UI you need. Today that starts with copy and paste. A future CLI eject command will automate the copying.
+
 [Customize skins](../how-to/customize-skins.md)
 
 ### AI-native DX

package/docs/how-to/add-a-background-video.md

@@ -0,0 +1,210 @@
+# Add a background video
+
+Add an accessible background video from an MP4, WebM, HLS, or Mux source
+
+Add a decorative video behind your page content. Start with an MP4 or WebM file, which browsers can play directly. If your video is delivered as HLS, use the HLS or Mux option below.
+
+## Recommended approach
+
+Use [BackgroundVideo](../reference/background-video.md) with an MP4 or WebM URL. Put the video and poster inside a wrapper with `aria-hidden="true"` because both are decorative. Keep the heading, links, and other page content outside that wrapper.
+
+![](https://image.mux.com/601n4w1fq88NJiVpzvrQQeQfNnnjjfKMIN7dCGAEarTs/thumbnail.webp)
+
+### Build the next great video experience
+
+[Compare source options](#common-variations)
+
+App.tsx
+
+App.css
+
+```
+import { BackgroundVideo } from '@videojs/react/media/background-video';
+
+export default function BasicUsage() {
+  return (
+    <section className="add-background-video-react-demo">
+      <div className="add-background-video-react-demo__visual" aria-hidden="true">
+        <img className="add-background-video-react-demo__poster" src="https://image.mux.com/601n4w1fq88NJiVpzvrQQeQfNnnjjfKMIN7dCGAEarTs/thumbnail.webp" alt="" />
+        <BackgroundVideo className="add-background-video-react-demo__media" src="https://stream.mux.com/601n4w1fq88NJiVpzvrQQeQfNnnjjfKMIN7dCGAEarTs/highest.mp4" />
+      </div>
+      <div className="add-background-video-react-demo__content">
+        <h3>Build the next great video experience</h3>
+        <a href="#common-variations">Compare source options</a>
+      </div>
+    </section>
+  );
+}
+```
+```
+.add-background-video-react-demo {
+  position: relative;
+  display: grid;
+  min-height: 18rem;
+  overflow: hidden;
+  color: white;
+  background: black;
+  border-radius: 0.5rem;
+  isolation: isolate;
+}
+
+.add-background-video-react-demo__visual,
+.add-background-video-react-demo__poster,
+.add-background-video-react-demo__media {
+  position: absolute;
+  inset: 0;
+  width: 100%;
+  height: 100%;
+}
+
+.add-background-video-react-demo__visual {
+  pointer-events: none;
+}
+
+.add-background-video-react-demo__visual::after {
+  position: absolute;
+  inset: 0;
+  content: "";
+  background: linear-gradient(90deg, rgb(0 0 0 / 85%), rgb(0 0 0 / 55%));
+}
+
+.add-background-video-react-demo__poster,
+.add-background-video-react-demo__media {
+  display: block;
+  object-fit: cover;
+}
+
+.add-background-video-react-demo__media {
+  --media-object-fit: cover;
+  --media-object-position: center;
+}
+
+.add-background-video-react-demo__content {
+  position: relative;
+  z-index: 1;
+  display: grid;
+  gap: 1rem;
+  place-content: end start;
+  max-width: 28rem;
+  padding: 2rem;
+}
+
+.add-background-video-react-demo__content h3 {
+  margin: 0;
+  font-size: 1.75rem;
+  line-height: 1.1;
+}
+
+.add-background-video-react-demo__content a {
+  width: fit-content;
+  padding: 0.625rem 1rem;
+  color: black;
+  text-decoration: none;
+  background: white;
+  border-radius: 0.25rem;
+}
+
+.add-background-video-react-demo__content a:focus-visible {
+  outline: 0.2rem solid white;
+  outline-offset: 0.2rem;
+}
+
+@media (prefers-reduced-motion: reduce) {
+  .add-background-video-react-demo__media {
+    display: none;
+  }
+}
+```
+
+## How it works
+
+BackgroundVideo renders the browser’s `<video>` element and starts it muted, looped, autoplaying, and inline. The example puts that video and an empty-alt poster in the `.hero-visual` wrapper. The wrapper is hidden from assistive technology and ignores pointer input, so it does not act like a media player.
+
+The page defines the hero’s size. The video fills that space with `--media-object-fit: cover`, while the poster remains visible until the video paints a frame. The reduced-motion rule hides the video and leaves the poster in place.
+
+Set the size, position, and transforms on the `.hero-visual` wrapper so the poster and video stay together.
+
+## Availability and constraints
+
+*   Use a source the browser can play directly, such as MP4 or WebM.
+*   Safari can play HLS URLs directly. Other browsers cannot do so reliably, so use an HLS variation below when the same `.m3u8` URL must work across browsers.
+*   BackgroundVideo does not create a poster or report analytics. Keep the poster in your page and add analytics only when you need them.
+*   Video.js does not apply a reduced-motion policy for you. The example stops the decoration with `prefers-reduced-motion`.
+*   If the video communicates information, remove `aria-hidden`, give it an accessible name and controls, and use a regular video player.
+
+## Common variations
+
+Choose a variation based on the source you already have:
+
+Need
+
+Use
+
+Cross-browser HLS with a small background-only player
+
+[HlsBackgroundVideo](../reference/hls-background-video.md)
+
+The same background-only player for a Mux HLS URL
+
+[MuxBackgroundVideo](../reference/mux-background-video.md)
+
+### Play an HLS video
+
+HlsBackgroundVideo plays an HLS video without adding controls, audio, or captions. Pass a complete HLS URL through `src`:
+
+tsx
+
+```
+import { HlsBackgroundVideo } from '@videojs/react/media/hls-background-video';
+
+<HlsBackgroundVideo
+  className="hero-media"
+  src="https://media.example.com/hero.m3u8"
+  crossOrigin="anonymous"
+  onError={() => console.error('The background stream could not play')}
+/>
+```
+
+Your HLS stream must be unencrypted and use fragmented MP4 video segments, also called fMP4 or CMAF. The component chooses one video size when playback starts and does not switch sizes later. It cannot play older MPEG-TS segments.
+
+### Play a Mux HLS URL
+
+MuxBackgroundVideo is a Mux-named alias for HlsBackgroundVideo. Pass a complete Mux HLS URL, not a bare playback ID or `source` object:
+
+tsx
+
+```
+import { MuxBackgroundVideo } from '@videojs/react/media/mux-background-video';
+
+<MuxBackgroundVideo
+  className="hero-media"
+  src="https://stream.mux.com/PLAYBACK_ID.m3u8?max_resolution=720p"
+  crossOrigin="anonymous"
+/>
+```
+
+This component does not create a Mux poster, preview thumbnails, or analytics session. Keep the poster in your page and add analytics separately when you need them.
+
+## Troubleshooting
+
+### An HLS URL works in Safari but not another browser
+
+BackgroundVideo hands its `src` to the browser’s `<video>` element. Use HlsBackgroundVideo for a supported fMP4 HLS source, or MuxBackgroundVideo for a Mux HLS URL.
+
+### The video does not fill or follow transforms
+
+Set the size, transforms, and measurements on the wrapper that contains the video and poster. Size the background-video component to fill that wrapper.
+
+### No poster or Mux analytics appear
+
+The background-video components do not provide them. Render an empty-alt poster in the same wrapper as the video, and add analytics separately.
+
+## Related components
+
+*   [BackgroundVideo](../reference/background-video.md)
+*   [HlsBackgroundVideo](../reference/hls-background-video.md)
+*   [MuxBackgroundVideo](../reference/mux-background-video.md)
+
+## Related guides
+
+*   [Add a poster and loading placeholder](./add-a-poster-and-loading-placeholder.md)

package/docs/how-to/add-a-poster-and-loading-placeholder.md

@@ -0,0 +1,187 @@
+# Add a poster and loading placeholder
+
+Set the image shown before playback, then add a lightweight placeholder while it loads
+
+A poster is the image shown before your video plays. Set one on the player. If it loads slowly, add a small placeholder so the player does not start as empty space.
+
+## Set a poster
+
+Set the player’s `poster` to an image URL:
+
+tsx
+
+```
+import '@videojs/react/video/skin.css';
+import { Video, VideoPlayer, VideoSkin } from '@videojs/react/video';
+
+export function MyPlayer() {
+  return (
+    <VideoPlayer poster="/poster.jpg">
+      <VideoSkin>
+        <Video src="/video.mp4" playsInline />
+      </VideoSkin>
+    </VideoPlayer>
+  );
+}
+```
+
+If you use a ready-made skin, it includes [Poster](../reference/poster.md) and shows the image automatically. If you build your own UI, add Poster yourself. It hides after the user plays or seeks.
+
+Posters are decorative by default, with an empty `alt`. If the image communicates something that is not available elsewhere, add `alt` text when you customize the poster image.
+
+## Add a loading placeholder
+
+A placeholder is a tiny preview that appears while the poster downloads. Keep it small enough to include with the page, such as a short data URL.
+
+### Use your framework’s image component
+
+If you use `VideoSkin`, pass your framework’s image component to `renderPoster`. Video.js passes the poster URL as `src`.
+
+tsx
+
+```
+import '@videojs/react/video/skin.css';
+import { Video, VideoPlayer, VideoSkin } from '@videojs/react/video';
+import NextImage from 'next/image';
+
+export function MyPlayer() {
+  return (
+    <VideoPlayer poster="/poster.jpg">
+      <VideoSkin
+        renderPoster={({ src, ...props }) =>
+          src ? (
+            <NextImage
+              {...props}
+              src={src}
+              alt=""
+              fill
+              placeholder="blur"
+              blurDataURL="data:image/webp;base64,…"
+            />
+          ) : null
+        }
+      >
+        <Video src="/video.mp4" playsInline />
+      </VideoSkin>
+    </VideoPlayer>
+  );
+}
+```
+
+Next.js generates blur data for static imports. Here, the poster URL arrives while the player runs, so provide `blurDataURL` yourself.
+
+### Use a plain image
+
+For more control, add the placeholder as a background on the image that `VideoSkin` draws:
+
+tsx
+
+```
+import '@videojs/react/video/skin.css';
+import { Video, VideoPlayer, VideoSkin } from '@videojs/react/video';
+
+export function MyPlayer() {
+  return (
+    <VideoPlayer poster="/poster.jpg">
+      <VideoSkin
+        renderPoster={(props) => (
+          <img
+            {...props}
+            style={{
+              ...props.style,
+              background:
+                "url('data:image/webp;base64,…') var(--media-object-position, center) / contain no-repeat",
+            }}
+          />
+        )}
+      >
+        <Video src="/video.mp4" playsInline />
+      </VideoSkin>
+    </VideoPlayer>
+  );
+}
+```
+
+The examples use `contain` for both images. Use `cover` for both when the poster should fill the player. Keeping the same size and position prevents the image from jumping when the poster appears.
+
+## Let the media choose a poster
+
+Some media components choose a poster for you. For example, `MuxVideo` creates one from its playback ID:
+
+tsx
+
+```
+import '@videojs/react/video/skin.css';
+import { MuxVideo } from '@videojs/react/media/mux-video';
+import { VideoPlayer, VideoSkin } from '@videojs/react/video';
+
+export function MyPlayer() {
+  return (
+    <VideoPlayer>
+      <VideoSkin>
+        <MuxVideo
+          source={{
+            playbackId: 'BV3YZtogl89mg9VcNBhhnHm02Y34zI1nlMuMQfAbl3dM',
+            poster: { time: 2 },
+          }}
+          playsInline
+        />
+      </VideoSkin>
+    </VideoPlayer>
+  );
+}
+```
+
+When the player and media component both choose a poster, the player’s `poster` wins. See [Metadata](../reference/feature-metadata.md) for how the player combines those values.
+
+## Add a poster to your own UI
+
+When your UI already includes Poster, apply the same placeholder directly:
+
+tsx
+
+```
+<Poster
+  render={(props) => (
+    <img
+      {...props}
+      style={{
+        ...props.style,
+        background:
+          "url('data:image/webp;base64,…') var(--media-object-position, center) / contain no-repeat",
+      }}
+    />
+  )}
+/>
+```
+
+## Troubleshooting
+
+### No poster appears
+
+Check that the player has a `poster` or that the media component can create one from its source.
+
+### The final poster never appears
+
+Pass the `src` from `renderPoster` to your image. If your image component requires a source, return `null` until `src` is available.
+
+### The placeholder and poster use different crops
+
+Use the same fit for both images: pair `background-size: contain` with `object-fit: contain`, or use `cover` for both.
+
+### The placeholder adds too much page weight
+
+Use fewer pixels and stronger compression. The placeholder only needs to suggest the poster’s color and shape until the full image appears.
+
+## Related components
+
+*   [Poster](../reference/poster.md)
+
+## Related API
+
+*   [Metadata](../reference/feature-metadata.md)
+
+## Related guides
+
+*   [Customize skins](./customize-skins.md)
+*   [Build your own UI component](./build-your-own-component.md)

package/docs/how-to/add-keyboard-shortcuts-and-gestures.md

@@ -0,0 +1,97 @@
+# Add keyboard shortcuts and gestures
+
+Add keyboard shortcuts, tap and double-tap gestures, and on-screen feedback for input actions.
+
+Add keyboard shortcuts and pointer gestures to the player declaratively, with on-screen feedback and screen-reader announcements.
+
+Note
+
+Using a pre-built [skin](../concepts/skins.md)? It already includes the controls shown here. You may still need the media or player setup in this guide. The component examples are for building your own player UI from individual [components](../concepts/ui-components.md).
+
+## Recommended approach
+
+Declare shortcuts with `Hotkey` and gestures with `Gesture` inside the player container. Each maps an input to a player action; the prebuilt skins ship a full set.
+
+tsx
+
+```
+import { Container, Gesture, Hotkey } from '@videojs/react';
+import { Video, VideoPlayer } from '@videojs/react/video';
+
+export default function App() {
+  return (
+    <VideoPlayer>
+      <Container>
+        <Video src="https://stream.mux.com/BV3YZtogl89mg9VcNBhhnHm02Y34zI1nlMuMQfAbl3dM/highest.mp4" muted playsInline />
+
+        <Hotkey keys="Space" action="togglePaused" />
+        <Hotkey keys="m" action="toggleMuted" />
+        <Hotkey keys="f" action="toggleFullscreen" />
+        <Hotkey keys="ArrowRight" action="seekStep" value={5} />
+        <Hotkey keys="ArrowLeft" action="seekStep" value={-5} />
+
+        <Gesture type="tap" action="togglePaused" pointer="mouse" region="center" />
+        <Gesture type="tap" action="toggleControls" pointer="touch" />
+        <Gesture type="doubletap" action="seekStep" value={-10} region="left" />
+        <Gesture type="doubletap" action="seekStep" value={10} region="right" />
+      </Container>
+    </VideoPlayer>
+  );
+}
+```
+
+## How it works
+
+*   `Hotkey` binds keys to player actions: `togglePaused`, `toggleMuted`, `toggleFullscreen`, `toggleSubtitles`, `togglePictureInPicture`, `seekStep` and `volumeStep` (with a `value`), `seekToPercent`, `speedUp`, and `speedDown`. The actions call the same feature state actions your components use.
+*   `Gesture` binds pointer input — `tap` and `doubletap` — to the same actions, minus `seekToPercent` and plus `toggleControls`. Bindings are scoped by `pointer` (`mouse` or `touch`) and `region` (`left`, `center`, `right`) — regions split the container’s width, not the rendered video’s — so double-tap-left rewinds while double-tap-right skips forward.
+*   `StatusAnnouncer` announces action results to screen readers, and the input indicator components render transient on-screen feedback (volume level, captions on/off) the way native players do. The prebuilt skins wire these up.
+
+The prebuilt skins bind the conventional set: Space and `k` toggle playback, `m` mutes, `f` fullscreens, `c` toggles captions, `i` toggles picture-in-picture, arrows seek and change volume, `j`/`l` seek in larger steps, `0`–`9` jump to a percentage, and `<`/`>` change speed.
+
+## Availability and constraints
+
+*   Hotkeys listen on the player container by default, so multiple players on a page don’t fight over keys. Pass `target="document"` on a hotkey to make it page-wide — appropriate only when one player owns the page.
+*   Typing is protected: while focus is in an editable field, single-key bindings are skipped automatically. Modifier combinations (for example `Ctrl+Shift+f`) still fire.
+*   Repeatable actions (seeking, volume) fire on held keys; toggle actions don’t repeat.
+*   Touch tap-to-toggle-controls and tap-to-pause are mutually exclusive per pointer type — the skins pause on mouse tap and toggle controls on touch tap, matching platform conventions.
+*   Gestures and the built-in touch handling coordinate through one recognizer; register gestures declaratively instead of adding raw pointer listeners next to them.
+
+## Common variations
+
+### Customize a shortcut
+
+Render your own `Hotkey` set instead of a skin’s: every binding is just an element, so add, remove, or re-key them freely.
+
+### Seek step size
+
+`seekStep` takes its step from `value` — match your content: 5 seconds for short clips, 15 or 30 for long-form.
+
+## Troubleshooting
+
+### Shortcuts don’t fire
+
+Focus is outside the player container. Click the player first, or move focus into it; hotkeys are player-scoped by design.
+
+### Double-tap seek also toggles pause
+
+Regions overlap: keep single-tap `togglePaused` on `center` only, and double-tap seek on `left` and `right`, as in the skin defaults.
+
+### No visual feedback on keyboard actions
+
+The input indicator components render that feedback; use a prebuilt skin or add `StatusAnnouncer` and the indicator components from the skin source to a custom UI.
+
+## Related components
+
+*   [Controls](../reference/controls.md)
+*   [Tooltip](../reference/tooltip.md)
+
+## Related API
+
+*   [Playback feature](../reference/feature-playback.md)
+*   [Volume feature](../reference/feature-volume.md)
+*   [Fullscreen feature](../reference/feature-fullscreen.md)
+
+## Related guides
+
+*   [Automatically show and hide controls](./show-and-hide-controls.md)
+*   [Accessibility](../concepts/accessibility.md)