@7365admin1/layer-common 3.2.2-staging.146 → 3.2.2-staging.147

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.
@@ -201,9 +201,21 @@ const selectItem = (value: string) => {
201
201
  color: var(--text);
202
202
  }
203
203
 
204
- .switch-context__panel {
205
- border-radius: var(--r-menu);
206
- box-shadow: var(--shadow-menu);
204
+ /* The panel is a `v-card`, and Vuetify puts it inside `.v-overlay__content`.
205
+ `screens.css` gives EVERY card in an overlay the modal shape - 16px and the
206
+ modal shadow - with `!important`, because dialogs open from sixty components
207
+ and the shape had to be stated once. A menu is an overlay too, so the panel
208
+ was silently taking the modal shape: measured 16px and
209
+ `rgba(10, 12, 16, 0.3) 0 24px 64px`, not the 14px `--r-menu` and the lighter
210
+ `--shadow-menu` it asks for.
211
+ `!important` alone does NOT win it back: `.switch-context__panel[data-v-...]`
212
+ and `.v-overlay__content > .v-card` are both two classes, the scope attribute
213
+ counts, and a tie goes to whichever sheet loaded last - which is screens.css.
214
+ Measured still 16px with `!important` on the plain class. So the selector
215
+ carries the overlay class too, to out-specify rather than tie. */
216
+ .v-overlay__content > .switch-context__panel {
217
+ border-radius: var(--r-menu) !important;
218
+ box-shadow: var(--shadow-menu) !important;
207
219
  border: 1px solid var(--border);
208
220
  background: var(--card);
209
221
  padding: 14px;
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.146",
5
+ "version": "3.2.2-staging.147",
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.",