@oddin-gg/havik-player 2.25.0 → 2.25.1

package/docs/API.md

@@ -494,14 +494,19 @@ failure while "online" keeps its ordinary retry path.
 
 What happens on a network loss, by layer:
 
-- **hls.js engine**: a fatal network error with no HTTP status that lands while
-  the browser says offline parks the loader instead of spending the five-attempt
-  retry budget on requests that cannot succeed; the end-of-stream and starvation
-  watchdogs stand down with it, so a long drop is never read as the stream's end.
-  The `online` event restarts it at once, budget refunded, with hls.js, the
-  buffer and the DRM key sessions all still in place, so a short drop resumes in
-  a part or two rather than through a full re-attach. A failure that carries a
-  status is the origin's answer and is never parked.
+- **hls.js engine**: the browser's `offline` event engages a hold at once: the
+  end-of-stream and starvation watchdogs stand down (a playlist that cannot be
+  fetched is not a stream that ended), and a fatal network error with no HTTP
+  status parks the loader instead of spending the five-attempt retry budget.
+  The hold keys off the browser's signal because hls.js itself may never raise
+  a fatal error during an outage: measured in Chromium, it sits in its own
+  playlist-retry backoff for the whole of a 20 s loss. The `online` event
+  releases the hold, refunds the budget and restarts the loader right away,
+  with hls.js, the buffer and the DRM key sessions all still in place: measured
+  in Chromium against a local live stream, the offline card is up 5 ms after
+  the loss and playback is back 120 ms after the link returns, through one
+  resolve for the whole session. A failure that carries a status is the
+  origin's answer and is never parked.
 - **Native engine (Safari)**: the element reports one opaque error for
   everything; while the browser says offline it is typed `NETWORK`, and the
   managed player re-attaches on `online`.

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.25.0/dist/havik-player.global.js" integrity="sha384-Q5KzgOEvnd+a/0dfEEovWiaTdruyt7ADjHF+VrOdCwBVYwhc7NwWxlr/1WOixrVc" crossorigin="anonymous"></script>
+    <script src="https://cdn.jsdelivr.net/npm/@oddin-gg/havik-player@2.25.1/dist/havik-player.global.js" integrity="sha384-yWIIiYBGAmMNuObEaCqXU3CpnniQZuR2ZsjYW/6rbXx6pC+nM9r5RyK4UaJuCDQM" 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.25.0/dist/havik-player.global.js" integrity="sha384-Q5KzgOEvnd+a/0dfEEovWiaTdruyt7ADjHF+VrOdCwBVYwhc7NwWxlr/1WOixrVc" crossorigin="anonymous"></script>
+    <script src="https://cdn.jsdelivr.net/npm/@oddin-gg/havik-player@2.25.1/dist/havik-player.global.js" integrity="sha384-yWIIiYBGAmMNuObEaCqXU3CpnniQZuR2ZsjYW/6rbXx6pC+nM9r5RyK4UaJuCDQM" crossorigin="anonymous"></script>
     <script>
       (async () => {
         const player = await HavikPlayer.createPlayer({

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@oddin-gg/havik-player",
-  "version": "2.25.0",
+  "version": "2.25.1",
   "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,