@ethisyscore/plugin-ui 1.74.0 → 1.76.0
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.
- package/dist/platform-react/index.cjs +28 -9
- package/dist/platform-react/index.cjs.map +1 -1
- package/dist/platform-react/index.d.cts +2 -0
- package/dist/platform-react/index.d.ts +2 -0
- package/dist/platform-react/index.js +28 -9
- package/dist/platform-react/index.js.map +1 -1
- package/package.json +1 -1
- package/styles/plugin-base.css +11 -0
package/package.json
CHANGED
package/styles/plugin-base.css
CHANGED
|
@@ -86,4 +86,15 @@
|
|
|
86
86
|
width: 0;
|
|
87
87
|
height: 0;
|
|
88
88
|
z-index: 1300;
|
|
89
|
+
/* Keep portaled overlays interactive even when the surface root is a
|
|
90
|
+
pointer-events:none passthrough. A PlatformReactOverlay mounts inside a host
|
|
91
|
+
portal root the host sets `pointer-events: none` on (so the overlay's empty
|
|
92
|
+
viewport region lets clicks fall through to the page underneath); the portal
|
|
93
|
+
container then INHERITS that `none`, and every menu/popover/tooltip/dialog it
|
|
94
|
+
hosts becomes unclickable and un-dismissable except by keyboard. Re-enabling
|
|
95
|
+
it here fixes that for every overlay. It is a no-op on routed pages (their
|
|
96
|
+
surface root is not passthrough, so this is the inherited default anyway), and
|
|
97
|
+
the 0x0 container takes no clicks itself — only its overflowing overlay
|
|
98
|
+
children do. */
|
|
99
|
+
pointer-events: auto;
|
|
89
100
|
}
|