@refrakt-md/skeleton 0.22.0 → 0.24.0

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@refrakt-md/skeleton",
   "description": "The structural cascade layer + layer-order contract every refrakt theme builds on — ships `@layer skeleton` and the `@layer skeleton, skin;` order declaration, plus the token-name contract",
-  "version": "0.22.0",
+  "version": "0.24.0",
   "type": "module",
   "license": "MIT",
   "repository": {
@@ -29,7 +29,7 @@
     "styles"
   ],
   "dependencies": {
-    "@refrakt-md/types": "0.22.0"
+    "@refrakt-md/types": "0.24.0"
   },
   "scripts": {
     "build": "tsc"

package/styles/dimensions/guest-posture.css

@@ -17,3 +17,11 @@
 [data-section="media"][data-guest-posture="presentational"] :is(.rf-tabs__tabs, .rf-codegroup__tabs) {
 	display: none;
 }
+
+/* SPEC-104 — a `backdrop` guest (a live sandbox in the bg layer) is inert at the
+ * pointer: decoration behind content, never an interaction target. Unlike
+ * `presentational`, the behaviours layer still mounts it (it must run) — this rule
+ * only suppresses interaction. */
+[data-guest-posture="backdrop"] {
+	pointer-events: none;
+}

package/styles/runes/bg.css

@@ -17,6 +17,14 @@
 	object-fit: cover;
 	object-position: var(--bg-position, center);
 }
+/* SPEC-104 — a live sandbox backdrop fills the bg layer like bg-video, beneath
+ * the overlay/scrim appended after it (which stack above by source order). */
+[data-name="bg"] > [data-bg-guest] {
+	position: absolute;
+	inset: 0;
+	width: 100%;
+	height: 100%;
+}
 [data-name="bg-overlay"] {
 	position: absolute;
 	inset: 0;

package/styles/runes/datatable.css

@@ -1,6 +1,6 @@
-/* datatable — structure. The toolbar + pagination flex rows and the full-width
- * search input. The table chrome, type, borders, and the table overflow/width
- * overrides (which override the table element wrapper by source order) stay skin
+/* datatable — structure. The toolbar + pagination flex rows, the full-width
+ * search input, and the table scroll container that lets wide tables overflow
+ * horizontally on narrow screens. The table chrome, type, and borders stay skin
  * (Lumina's styles/runes/datatable.css). */
 
 .rf-datatable__toolbar {
@@ -9,6 +9,12 @@
 .rf-datatable__input {
 	width: 100%;
 }
+/* Scroll wrapper around the table — toolbar/pagination sit outside this so they
+ * stay anchored to the viewport while the table itself scrolls horizontally. */
+.rf-datatable__scroll {
+	overflow-x: auto;
+	-webkit-overflow-scrolling: touch;
+}
 .rf-datatable__pagination {
 	display: flex;
 	align-items: center;

package/styles/runes/mockup.css

@@ -43,6 +43,33 @@
 	zoom: calc(var(--mockup-scale, 1) * min(1, tan(atan2(100cqi, var(--mockup-device-width, 100cqi)))));
 }
 
+/* Media guest: fill the slot. The slot, not the device, sets the size here, so
+ * the device scales (up or down) so its width matches the slot's; the cell's
+ * fixed height + overflow then crops any vertical overflow (a tall phone peeks,
+ * a wide laptop fits whole).
+ *
+ * The scale factor is `slotWidth ÷ deviceWidth`, but it is *not* computed here:
+ * deriving it from container-query units mis-resolves on iOS WebKit (under
+ * `zoom` the device balloons; even under `transform` `cqi` resolves to the wrong
+ * size). The `mockup` behavior measures the slot in JS — deterministic across
+ * engines — and publishes the factor as `--mockup-fit-scale`; centering and the
+ * clip stay here. Without JS the factor defaults to 1 (native size), which
+ * degrades gracefully. `transform` (not `zoom`) so it never feeds back into the
+ * container's measured size.
+ *
+ * `left` re-centers the native layout box for any slot/device width (the box is
+ * left-aligned at native width; the offset shifts its centre onto the slot's),
+ * and `transform-origin: top center` anchors the device's top so the clip eats
+ * the bottom. `fit="none"` opts out (its own transform path above); standalone
+ * mockups keep the capped base zoom (a phone shouldn't fill a column). */
+[data-section="media"] > .rf-mockup:not([data-fit="none"]) .rf-mockup__frame {
+	zoom: normal;
+	margin-inline: 0;
+	left: calc((100% - var(--mockup-device-width, 100%)) / 2);
+	transform: scale(calc(var(--mockup-scale, 1) * var(--mockup-fit-scale, 1)));
+	transform-origin: top center;
+}
+
 .rf-mockup__viewport {
 	overflow: auto;
 }

package/styles/runes/preview.css

@@ -38,8 +38,8 @@
 	z-index: 1;
 }
 .rf-preview__source-tabs { display: flex; }
-@container (max-width: 1280px) {
-	.rf-preview--in-feature {
-		margin-inline: calc(-1 * var(--rf-content-gutter, 1.5rem));
-	}
-}
+/* The in-feature breakout (`.rf-preview--in-feature { margin-inline: -gutter }`)
+ * is NOT here: it overrides the skin rule `.rf-preview { margin: 2rem 0 }` by
+ * specificity, so it must stay in @layer skin — in @layer skeleton it loses to
+ * that skin margin (skin beats skeleton regardless of specificity) and the bleed
+ * is nullified. It lives in Lumina's preview.css @container block. */