@fusion.dev/helix 0.17.1 → 0.18.0

package/custom-elements.json

@@ -9030,7 +9030,8 @@
                 "slug": "linked"
               },
               {
-                "description": "Glass, which is a pair: a ground that lets light through and a filter behind it.",
+                "description": "The three materials over one ground, each a pair: a translucent fill and a filter behind it.",
+                "min": 520,
                 "slug": "material"
               },
               {
@@ -45586,6 +45587,11 @@
                 "description": "Two series on one scale, with a legend mapping the same palette.",
                 "slug": "several-series"
               },
+              {
+                "description": "A window that slides: a reading arrives, the oldest leaves, and the line marches.",
+                "min": 420,
+                "slug": "streaming"
+              },
               {
                 "description": "The same chart given different numbers, moving to the new shape rather than snapping to it.",
                 "slug": "taking-new-data"
@@ -101295,6 +101301,17 @@
                 "module": "src/video/root/video-root.ts"
               }
             },
+            {
+              "kind": "field",
+              "name": "handlePicture",
+              "privacy": "private",
+              "readonly": true,
+              "description": "A press on the picture plays or pauses it.\n\n**The picture is the biggest target a player has**, and on every other\nplayer a reader has used it is the one that stops the thing. A component\nthat spends the whole frame on a video and then asks for a 32 pixel button\nis one that works only for people who know where the button is.\n\n**Two cases where it must not.** The first is `controls`, where the browser\ndraws its own bar over the picture and owns what a press on it means: acting\nas well would toggle twice, once here and once in the UA, which cancels out\nand looks broken.\n\nThe second is a player whose chrome has gone idle. There, the first press is\nasking for the controls back rather than asking to pause, which is what\nevery touch player does: `stir` brings them, and the press is spent. A\nsecond press, with the bar showing, means what it says. This is also why the\ncheck is `idle` rather than a pointer-type test: it is the same answer for a\nmouse left resting until the bar faded.",
+              "inheritedFrom": {
+                "name": "HelixHeadlessVideo",
+                "module": "src/video/root/video-root.ts"
+              }
+            },
             {
               "kind": "field",
               "name": "handleFullscreenChange",

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@fusion.dev/helix",
   "description": "Styled component tier. Extends the headless tier with token-driven presentation.",
-  "version": "0.17.1",
+  "version": "0.18.0",
   "license": "MIT",
   "author": "Ross Sheppard <ross.sheppard@fusion.dev>",
   "repository": {
@@ -46,14 +46,14 @@
   },
   "bugs": "https://github.com/project-fusion/fusion/issues",
   "dependencies": {
-    "@fusion.dev/helix-core": "0.17.1",
-    "@fusion.dev/helix-headless": "0.17.1",
-    "@fusion.dev/helix-styles": "0.17.1"
+    "@fusion.dev/helix-core": "0.18.0",
+    "@fusion.dev/helix-headless": "0.18.0",
+    "@fusion.dev/helix-styles": "0.18.0"
   },
   "devDependencies": {
     "@custom-elements-manifest/analyzer": "^0.11.0",
-    "@fusion.dev/helix-cem": "0.17.1",
-    "@fusion.dev/helix-testing": "0.17.1",
+    "@fusion.dev/helix-cem": "0.18.0",
+    "@fusion.dev/helix-testing": "0.18.0",
     "@fusion.dev/scripts": "0.0.0-dev",
     "@happy-dom/global-registrator": "^20.0.0",
     "@lit-labs/ssr": "^3.3.0",