@7365admin1/layer-common 3.2.2-staging.162 → 3.2.2-staging.164

package/assets/css/screens.css

@@ -456,6 +456,21 @@
   letter-spacing: 0;
   text-transform: none;
   color: var(--text2);
+  /*
+   * THE EDGE IS THE GHOST. The handoff draws this button as "40px, 1px border,
+   * card fill" - the border is what separates it from the page, since the fill
+   * is the same `--card` as the surface behind it.
+   *
+   * `border-color` alone does not draw anything. It only tinted an edge that
+   * Vuetify's `variant` had already decided the width of: `outlined` gives
+   * `thin`, `flat` gives 0. So the same class rendered a bordered button at 48
+   * call sites and a borderless one at 13 - measured 1px vs 0px, both themes -
+   * and which you got depended on a `variant` a caller had no reason to think
+   * was load-bearing. Naming the width here makes the class draw the design's
+   * button whichever variant it is paired with.
+   */
+  border-width: 1px;
+  border-style: solid;
   border-color: var(--border);
   background: var(--card);
 }
@@ -737,6 +752,20 @@
   font-weight: var(--fw-btn);
   letter-spacing: 0;
   color: var(--text2);
+  /*
+   * Same reason as `.screen-btn-ghost` (#1200): `border-color` alone draws
+   * nothing, it only tints an edge whose width the Vuetify `variant` decided.
+   * Measured: paired with `outlined` this rule gives 1px, paired with `flat`
+   * it gives 0px - and the fill is `--card`, the same colour as the surface
+   * behind it, so a borderless copy has no boundary at all.
+   *
+   * The one call site today (`TableMain.vue`, Scan QR Code) does use
+   * `outlined`, so nothing is visibly broken right now. This is the latent
+   * half of the same defect: the next caller who writes `flat` gets an
+   * invisible button and no error. Naming the width closes it.
+   */
+  border-width: 1px;
+  border-style: solid;
   border-color: var(--border);
   background: var(--card);
 }

package/package.json

@@ -2,7 +2,7 @@
   "name": "@7365admin1/layer-common",
   "license": "MIT",
   "type": "module",
-  "version": "3.2.2-staging.162",
+  "version": "3.2.2-staging.164",
   "author": "7365admin1",
   "main": "./nuxt.config.ts",
   "//files": "What a consumer extending this layer actually loads. Without this npm ships the whole working tree - the changesets, the CI workflows, the render harness in tools/ and any scratch directory that happened to exist at publish time. Nuxt resolves a layer by directory, so every runtime directory below has to stay listed; adding a new top-level runtime directory means adding it here too.",