@ng-prism/plugin-visual-regression 22.2.0-beta.1 → 22.2.0-beta.2

package/dist/vrt-bg.d.ts

@@ -3,18 +3,20 @@ import type { VrtVariantResult } from './visual-regression.types.js';
 /**
  * Background declarations for the box that holds a capture.
  *
- * The captures themselves are opaque, so this is mostly invisible — except
- * under a diff mask, where the unchanged pixels a comparator leaves
- * transparent let it through. There the surface decides whether a diff reads
- * as a diff or as a chequered mess.
+ * Mostly invisible behind an opaque capture — but not behind every one. It
+ * shows through a diff mask, where the unchanged pixels a comparator leaves
+ * transparent let it past, and through a `transparent` capture, which is see-
+ * through by design. In both places the surface decides whether the image
+ * reads as itself or as a chequered mess.
  *
- * Only `light` and `dark` produce a colour. `dots`, `plain` and `checker` all
- * paint `--prism-bg-surface`, a *theme* token, and the panel cannot know which
- * theme the runner's browser ran in — so those keep the checkerboard, which
- * reads as "transparent" rather than as a guess painted as fact. For `checker`
- * that is also the literal rendering, and since it is what an undeclared
- * variant resolves to, an undeclared capture frames itself correctly. Same for
- * a report that recorded no background at all.
+ * Only `light` and `dark` produce a colour. The rest keep the checkerboard,
+ * for two different reasons. `dots`, `plain` and `checker` paint
+ * `--prism-bg-surface`, a *theme* token, and the panel cannot know which theme
+ * the runner's browser ran in — so a colour here would be a guess painted as
+ * fact. `transparent` is the opposite case: its capture genuinely has an alpha
+ * channel, and the checkerboard is what makes that legible instead of
+ * inventing a surface the capture deliberately omitted. A report that recorded
+ * no background at all is treated the same way.
  */
 export declare function shotSurfaceStyle(bg: CanvasBg | undefined): Record<string, string>;
 /**

package/dist/vrt-bg.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"vrt-bg.d.ts","sourceRoot":"","sources":["../src/vrt-bg.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,QAAQ,EAAE,MAAM,uBAAuB,CAAC;AACtD,OAAO,KAAK,EAAE,gBAAgB,EAAE,MAAM,8BAA8B,CAAC;AAerE;;;;;;;;;;;;;;;GAeG;AACH,wBAAgB,gBAAgB,CAC9B,EAAE,EAAE,QAAQ,GAAG,SAAS,GACvB,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAIxB;AAED;;;;;;;;;;;;GAYG;AACH,wBAAgB,QAAQ,CACtB,OAAO,EAAE,gBAAgB,GACxB;IAAE,IAAI,EAAE,QAAQ,CAAC;IAAC,EAAE,EAAE,QAAQ,CAAA;CAAE,GAAG,IAAI,CAIzC"}
+{"version":3,"file":"vrt-bg.d.ts","sourceRoot":"","sources":["../src/vrt-bg.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,QAAQ,EAAE,MAAM,uBAAuB,CAAC;AACtD,OAAO,KAAK,EAAE,gBAAgB,EAAE,MAAM,8BAA8B,CAAC;AAerE;;;;;;;;;;;;;;;;;GAiBG;AACH,wBAAgB,gBAAgB,CAC9B,EAAE,EAAE,QAAQ,GAAG,SAAS,GACvB,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAIxB;AAED;;;;;;;;;;;;GAYG;AACH,wBAAgB,QAAQ,CACtB,OAAO,EAAE,gBAAgB,GACxB;IAAE,IAAI,EAAE,QAAQ,CAAC;IAAC,EAAE,EAAE,QAAQ,CAAA;CAAE,GAAG,IAAI,CAIzC"}

package/dist/vrt-bg.js

@@ -13,18 +13,20 @@ const SURFACE = {
 /**
  * Background declarations for the box that holds a capture.
  *
- * The captures themselves are opaque, so this is mostly invisible — except
- * under a diff mask, where the unchanged pixels a comparator leaves
- * transparent let it through. There the surface decides whether a diff reads
- * as a diff or as a chequered mess.
+ * Mostly invisible behind an opaque capture — but not behind every one. It
+ * shows through a diff mask, where the unchanged pixels a comparator leaves
+ * transparent let it past, and through a `transparent` capture, which is see-
+ * through by design. In both places the surface decides whether the image
+ * reads as itself or as a chequered mess.
  *
- * Only `light` and `dark` produce a colour. `dots`, `plain` and `checker` all
- * paint `--prism-bg-surface`, a *theme* token, and the panel cannot know which
- * theme the runner's browser ran in — so those keep the checkerboard, which
- * reads as "transparent" rather than as a guess painted as fact. For `checker`
- * that is also the literal rendering, and since it is what an undeclared
- * variant resolves to, an undeclared capture frames itself correctly. Same for
- * a report that recorded no background at all.
+ * Only `light` and `dark` produce a colour. The rest keep the checkerboard,
+ * for two different reasons. `dots`, `plain` and `checker` paint
+ * `--prism-bg-surface`, a *theme* token, and the panel cannot know which theme
+ * the runner's browser ran in — so a colour here would be a guess painted as
+ * fact. `transparent` is the opposite case: its capture genuinely has an alpha
+ * channel, and the checkerboard is what makes that legible instead of
+ * inventing a surface the capture deliberately omitted. A report that recorded
+ * no background at all is treated the same way.
  */
 export function shotSurfaceStyle(bg) {
     const surface = bg ? SURFACE[bg] : undefined;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ng-prism/plugin-visual-regression",
-  "version": "22.2.0-beta.1",
+  "version": "22.2.0-beta.2",
   "description": "Visual regression report panel for ng-prism.",
   "ng-add": {
     "save": "devDependencies"