itube-modern-player 0.8.0 → 0.8.2

package/dist/gesture-BLWiPHlW.cjs

@@ -0,0 +1,2 @@
+"use strict";function c(){const e=document.createElement("video");e.setAttribute("playsinline","");const t=e.play();return t&&t.catch(()=>{}),e}exports.createGestureVideo=c;
+//# sourceMappingURL=gesture-BLWiPHlW.cjs.map

package/dist/gesture-BLWiPHlW.cjs.map

@@ -0,0 +1 @@
+{"version":3,"file":"gesture-BLWiPHlW.cjs","sources":["../src/gesture.ts"],"sourcesContent":["/**\n * User-gesture media unlock, shared by the lazy entries (`createLazyPlayer`\n * and the Vue wrapper's `lazy` mode).\n *\n * Mobile browsers (iOS Safari first of all) allow `play()` with sound only\n * synchronously inside a user gesture — and the permission is granted PER\n * ELEMENT. The lazy flow crosses two async boundaries between the tap and the\n * autostart (the `import()` of the player chunk + the HLS attach), so a video\n * element created after them has no gesture attached: the first tap only\n * loaded the player and playback started on the second tap.\n *\n * The fix: create the `<video>` synchronously in the click handler and call\n * `play()` on it right there. Without a src it rejects immediately (that's\n * fine and expected), but the element keeps its user-activation flag — when\n * the player later attaches the real source to THIS element, `play()` with\n * sound goes through.\n */\nexport function createGestureVideo(): HTMLVideoElement {\n  const video = document.createElement('video')\n  video.setAttribute('playsinline', '')\n  const attempt = video.play()\n  // No source yet → the promise usually rejects (NotSupportedError); the\n  // play() CALL inside the gesture is what unlocks the element, not its\n  // success. NB: in some engines this promise stays PENDING until a source\n  // arrives and only resolves once REAL playback starts — so the success\n  // branch must be a no-op. (A `video.pause()` here paused the just-started\n  // video, killing the very autostart this helper exists for.)\n  if (attempt) attempt.catch(() => {})\n  return video\n}\n"],"names":["createGestureVideo","video","attempt"],"mappings":"aAiBO,SAASA,GAAuC,CACrD,MAAMC,EAAQ,SAAS,cAAc,OAAO,EAC5CA,EAAM,aAAa,cAAe,EAAE,EACpC,MAAMC,EAAUD,EAAM,KAAA,EAOtB,OAAIC,GAASA,EAAQ,MAAM,IAAM,CAAC,CAAC,EAC5BD,CACT"}

package/dist/gesture-BYJrYanO.js

@@ -0,0 +1,11 @@
+function c() {
+  const e = document.createElement("video");
+  e.setAttribute("playsinline", "");
+  const t = e.play();
+  return t && t.catch(() => {
+  }), e;
+}
+export {
+  c
+};
+//# sourceMappingURL=gesture-BYJrYanO.js.map

package/dist/gesture-BYJrYanO.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"gesture-BYJrYanO.js","sources":["../src/gesture.ts"],"sourcesContent":["/**\n * User-gesture media unlock, shared by the lazy entries (`createLazyPlayer`\n * and the Vue wrapper's `lazy` mode).\n *\n * Mobile browsers (iOS Safari first of all) allow `play()` with sound only\n * synchronously inside a user gesture — and the permission is granted PER\n * ELEMENT. The lazy flow crosses two async boundaries between the tap and the\n * autostart (the `import()` of the player chunk + the HLS attach), so a video\n * element created after them has no gesture attached: the first tap only\n * loaded the player and playback started on the second tap.\n *\n * The fix: create the `<video>` synchronously in the click handler and call\n * `play()` on it right there. Without a src it rejects immediately (that's\n * fine and expected), but the element keeps its user-activation flag — when\n * the player later attaches the real source to THIS element, `play()` with\n * sound goes through.\n */\nexport function createGestureVideo(): HTMLVideoElement {\n  const video = document.createElement('video')\n  video.setAttribute('playsinline', '')\n  const attempt = video.play()\n  // No source yet → the promise usually rejects (NotSupportedError); the\n  // play() CALL inside the gesture is what unlocks the element, not its\n  // success. NB: in some engines this promise stays PENDING until a source\n  // arrives and only resolves once REAL playback starts — so the success\n  // branch must be a no-op. (A `video.pause()` here paused the just-started\n  // video, killing the very autostart this helper exists for.)\n  if (attempt) attempt.catch(() => {})\n  return video\n}\n"],"names":["createGestureVideo","video","attempt"],"mappings":"AAiBO,SAASA,IAAuC;AACrD,QAAMC,IAAQ,SAAS,cAAc,OAAO;AAC5C,EAAAA,EAAM,aAAa,eAAe,EAAE;AACpC,QAAMC,IAAUD,EAAM,KAAA;AAOtB,SAAIC,KAASA,EAAQ,MAAM,MAAM;AAAA,EAAC,CAAC,GAC5BD;AACT;"}

package/dist/gesture.d.ts

@@ -0,0 +1,18 @@
+/**
+ * User-gesture media unlock, shared by the lazy entries (`createLazyPlayer`
+ * and the Vue wrapper's `lazy` mode).
+ *
+ * Mobile browsers (iOS Safari first of all) allow `play()` with sound only
+ * synchronously inside a user gesture — and the permission is granted PER
+ * ELEMENT. The lazy flow crosses two async boundaries between the tap and the
+ * autostart (the `import()` of the player chunk + the HLS attach), so a video
+ * element created after them has no gesture attached: the first tap only
+ * loaded the player and playback started on the second tap.
+ *
+ * The fix: create the `<video>` synchronously in the click handler and call
+ * `play()` on it right there. Without a src it rejects immediately (that's
+ * fine and expected), but the element keeps its user-activation flag — when
+ * the player later attaches the real source to THIS element, `play()` with
+ * sound goes through.
+ */
+export declare function createGestureVideo(): HTMLVideoElement;