@oddin-gg/havik-player 2.18.0 → 2.19.0

package/docs/API.md

@@ -394,6 +394,7 @@ interface Player {
   exitPictureInPicture(): Promise<void>;
   enterFullscreen(): Promise<boolean>; // element FS on the player container; iPhone → video-native. false = no mechanism
   exitFullscreen(): Promise<void>; // element or video-native; safe when not fullscreen
+  fullscreenSupported(): boolean; // false = permissions policy blocks it (iframe without allow=fullscreen) or no mechanism; optimistic before media loads on iPhone
   retry(): Promise<void>; // recover from an error (re-resolve + re-attach)
   reload(): Promise<void>; // re‑resolve playback (refreshes the license URL) + re‑attach
   on<E extends PlayerEvent>(event: E, cb: (payload: PlayerEventMap[E]) => void): () => void;
@@ -468,6 +469,17 @@ stream.
 > effect **after playback has started** (a tap on the pre-play poster is a
 > no-op there). Everywhere else (desktop, Android, iPad) the button uses
 > element fullscreen and keeps the branded controls.
+>
+> **Where fullscreen cannot work, the button is not shown** and the `f`
+> shortcut is inert, the same gate the Picture-in-Picture button has: a
+> cross-origin iframe whose `allow` list omits `fullscreen` (the browser
+> reports `document.fullscreenEnabled === false`), or a webview with no
+> fullscreen mechanism at all. So an operator who must block fullscreen on an
+> embed drops it from the iframe's `allow` attribute and needs no custom
+> control bar. The decision is re-made on the video's `loadedmetadata`, which
+> is when iPhone first reports whether its video-native presentation exists,
+> so on iPhone the button is still shown (and inert, as above) until playback
+> has started.
 
 ```ts
 type Controls = 'custom' | 'native' | 'none';
@@ -697,6 +709,7 @@ hls.attachMedia(videoElement);
 function enterVideoFullscreen(video: HTMLVideoElement, container?: HTMLElement): Promise<boolean>;
 function exitVideoFullscreen(video: HTMLVideoElement, container?: HTMLElement): Promise<void>;
 function videoFullscreenActive(video: HTMLVideoElement, container?: HTMLElement): boolean;
+function fullscreenSupported(video: HTMLVideoElement, container?: HTMLElement): boolean;
 ```
 
 Fullscreen with the platform quirks handled, so your own fullscreen button
@@ -716,7 +729,13 @@ first; it reports only through the video, never the document), is safe to
 call when not fullscreen, and is **scoped to your video's presentation**: an
 unrelated element's fullscreen elsewhere on the page is left alone.
 `videoFullscreenActive` tells you whether your video's presentation is
-currently fullscreen. Pass the same `container` to all three. For fullscreen **state changes**, listen to `fullscreenchange` /
+currently fullscreen. `fullscreenSupported` is the pre-flight for your button:
+`false` when a request is known to fail: the element API is there but the
+document reports `fullscreenEnabled === false` (permissions policy; an iframe
+without `fullscreen` in `allow`), or media is loaded and the platform has no
+mechanism at all. It stays `true` before media loads where no element API
+exists (iPhone cannot say yet), so re-check it on `loadedmetadata`. Pass the
+same `container` to all four. For fullscreen **state changes**, listen to `fullscreenchange` /
 `webkitfullscreenchange` on the document and `webkitbeginfullscreen` /
 `webkitendfullscreen` on the video; the last two are the only signal for
 iPhone's video-native fullscreen.

package/embed/index.html

@@ -28,7 +28,7 @@
            beacons endpoint can be derived and QoE analytics is silently off.
            `analytics` is honoured from the injected config only, never the query.
     -->
-    <script src="https://cdn.jsdelivr.net/npm/@oddin-gg/havik-player@2.18.0/dist/havik-player.global.js" integrity="sha384-bna/v7G8EjUwpvfY3vAwrzvlkh2RO3sMM8ccsC/A0LO1gYZyIluCR/6t5Mj8Qmmj" crossorigin="anonymous"></script>
+    <script src="https://cdn.jsdelivr.net/npm/@oddin-gg/havik-player@2.19.0/dist/havik-player.global.js" integrity="sha384-RWHZWgsgSqUcFMISDll7/ApdE2YOBYQ9C0xvHZo3OtY8AuU9OoSL5kOA3G29w/bg" crossorigin="anonymous"></script>
     <script>
       HavikPlayer.bootEmbed();
     </script>

package/examples/vanilla.html

@@ -12,7 +12,7 @@
          shipped in each npm release is pinned to that release with Subresource
          Integrity, injected at publish time (scripts/inject-sri.mjs). In
          production, always use a pinned + SRI'd tag like the released copy. -->
-    <script src="https://cdn.jsdelivr.net/npm/@oddin-gg/havik-player@2.18.0/dist/havik-player.global.js" integrity="sha384-bna/v7G8EjUwpvfY3vAwrzvlkh2RO3sMM8ccsC/A0LO1gYZyIluCR/6t5Mj8Qmmj" crossorigin="anonymous"></script>
+    <script src="https://cdn.jsdelivr.net/npm/@oddin-gg/havik-player@2.19.0/dist/havik-player.global.js" integrity="sha384-RWHZWgsgSqUcFMISDll7/ApdE2YOBYQ9C0xvHZo3OtY8AuU9OoSL5kOA3G29w/bg" crossorigin="anonymous"></script>
     <script>
       (async () => {
         const player = await HavikPlayer.createPlayer({

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@oddin-gg/havik-player",
-  "version": "2.18.0",
+  "version": "2.19.0",
   "description": "Havik HTML5 player SDK — LL-HLS + DRM playback for Oddin live streams (managed, bring-your-own-player, and iframe-embed modes).",
   "type": "module",
   "sideEffects": false,