@7365admin1/layer-common 3.2.2-staging.160 → 3.2.2-staging.161

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -398,6 +398,31 @@
398
398
  opacity: 0;
399
399
  }
400
400
 
401
+ /*
402
+ * DISABLED. The two rules above set `background` and `color` unconditionally,
403
+ * and they out-specify the treatment Vuetify would otherwise give a disabled
404
+ * button - so a Submit that a `v-form` has genuinely gated OFF was painting
405
+ * the full accent fill at full opacity, identical to a live one. Measured on
406
+ * `OnlineFormFill` with its required field emptied: enabled and disabled came
407
+ * back byte-identical (`rgb(75, 116, 196)` / `rgb(255, 255, 255)` /
408
+ * `opacity: 1`) on BOTH themes. The gate held; nothing showed it.
409
+ *
410
+ * 0.5 is the design's own disabled step - `.app-btn:disabled` in
411
+ * `primitives.css` uses it - so the two button families dim by the same amount
412
+ * rather than inventing a second number here.
413
+ *
414
+ * Both the attribute and Vuetify's class are named: `:disabled` is what a
415
+ * plain `<button>` carries, `.v-btn--disabled` is what Vuetify adds, and a
416
+ * rule that matched only one of them would go quiet the moment the other path
417
+ * was used.
418
+ */
419
+ .v-btn.screen-btn-primary:disabled,
420
+ .v-btn.screen-btn-primary.v-btn--disabled,
421
+ .v-btn.screen-btn-ghost:disabled,
422
+ .v-btn.screen-btn-ghost.v-btn--disabled {
423
+ opacity: 0.5;
424
+ }
425
+
401
426
  /**
402
427
  * The icon-only actions next to a primary button (download template, import,
403
428
  * export). The design draws an icon button as a bordered square the height of
package/package.json CHANGED
@@ -2,7 +2,7 @@
2
2
  "name": "@7365admin1/layer-common",
3
3
  "license": "MIT",
4
4
  "type": "module",
5
- "version": "3.2.2-staging.160",
5
+ "version": "3.2.2-staging.161",
6
6
  "author": "7365admin1",
7
7
  "main": "./nuxt.config.ts",
8
8
  "//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.",