@7365admin1/layer-common 4.2.2-staging.265 → 4.2.2-staging.266

package/assets/css/shell.css

@@ -256,3 +256,36 @@
     min-width: 44px;
   }
 }
+
+/**
+ * A toast must never take a click that was meant for the screen behind it.
+ *
+ * Every snackbar in the product is drawn at `z-index: 100000000` - the shared
+ * `Snackbar.vue` and both of `VisitorSocketPopUp.vue`'s - which is far above
+ * Vuetify's dialog stack (2000+). So a snackbar sits ON TOP of any dialog that
+ * is open, and its wrapper is a solid, `pointer-events: auto` box.
+ *
+ * Measured on staging, 1 Sep 2026: the realtime "New plate detected" toast
+ * landed over the Add Vehicle dialog's Submit button and swallowed the click,
+ * so on a busy gate - where a plate read arrives every few seconds - a vehicle
+ * could not be added at all. The tester could only finish the create by setting
+ * `pointer-events: none` on the snackbar by hand. It is not a vehicle problem:
+ * the same shared `Snackbar.vue` is mounted by 57 screens, so any toast that
+ * fires while any dialog is open can do this.
+ *
+ * The z-index is deliberately left alone - a camera-fault warning still has to
+ * be SEEN over a dialog. What changes is that only the toast's own controls
+ * take clicks; everything else passes through to whatever is underneath, which
+ * is exactly the behaviour the tester proved by hand.
+ */
+/* Two class names deep on purpose: Vuetify puts `v-overlay__content`, which
+   carries `pointer-events: auto`, on this same element. */
+.v-snackbar .v-snackbar__wrapper {
+  pointer-events: none;
+}
+
+.v-snackbar .v-snackbar__wrapper .v-btn,
+.v-snackbar .v-snackbar__wrapper a,
+.v-snackbar .v-snackbar__wrapper [role="button"] {
+  pointer-events: auto;
+}

package/package.json

@@ -2,7 +2,7 @@
   "name": "@7365admin1/layer-common",
   "license": "MIT",
   "type": "module",
-  "version": "4.2.2-staging.265",
+  "version": "4.2.2-staging.266",
   "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.",