@7365admin1/layer-common 3.2.2-staging.179 → 3.2.2-staging.180

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.
@@ -657,18 +657,6 @@
657
657
  white-space: nowrap;
658
658
  }
659
659
 
660
- /*
661
- * `--thead` is intentionally translucent. A fixed header, however, sits above
662
- * scrolling rows, so using the token by itself lets the first row show through
663
- * the header. Layer the same tint over the card surface to keep the rendered
664
- * colour unchanged while making the sticky header fully opaque.
665
- */
666
- .table-card .v-table--fixed-header thead th {
667
- background:
668
- linear-gradient(var(--thead), var(--thead)),
669
- var(--card) !important;
670
- }
671
-
672
660
  /**
673
661
  * ROW HEIGHT IS THE LINE BOX, NOT THE PADDING.
674
662
  *
@@ -173,13 +173,7 @@
173
173
  :style="`max-height: calc(100vh - (${offset}px))`"
174
174
  >
175
175
  <template v-for="(_, slotName) in $slots" #[slotName]="slotProps">
176
- <!--
177
- Vuetify invokes argument-less slots such as `no-data` with null
178
- props. Vue's dynamic `renderSlot` expects an object and otherwise
179
- crashes while reading `props.key`, leaving the previous route on
180
- screen even though Vue Router has already updated the URL.
181
- -->
182
- <slot :name="slotName" v-bind="slotProps ?? {}" />
176
+ <slot :name="slotName" v-bind="slotProps" />
183
177
  </template>
184
178
 
185
179
  <!--
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.179",
5
+ "version": "3.2.2-staging.180",
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.",