@ethisyscore/plugin-ui 1.59.0 → 1.62.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ethisyscore/plugin-ui",
-  "version": "1.59.0",
+  "version": "1.62.0",
   "description": "Plugin-UI umbrella SDK: client bridge + a11y/l10n primitives + brokered-MCP client (WI 4858).",
   "type": "module",
   "main": "./dist/index.cjs",

package/styles/plugin-base.css

@@ -53,9 +53,37 @@
    to `rounded-3xl` via CSS in its `components`/`utilities` layers, which can lose
    to MUI's 4px default inside a plugin's cascade. Pin the gogo radius here,
    unlayered + root-scoped (specificity 0,2,0) so it wins regardless of layer
-   placement. Portaled Paper (menus/dialogs/pickers) renders outside the root and
-   is unaffected — the host styles those. */
+   placement. Since portal containment landed, portaled Paper (menus/dialogs/
+   pickers) renders INSIDE the root too, so this now reaches those as well — the
+   same radius the host applies to its own. */
 .ehx-plugin-root .MuiCard-root,
 .ehx-plugin-root .MuiPaper-rounded {
   border-radius: var(--border-radius-3xl);
 }
+
+/* Portal container rendered by `PluginPortalScope` at the end of every plugin
+   surface. MUI's portalling components (Modal/Popper and everything built on
+   them) default to it, which keeps dialogs, menus, poppers and tooltips inside
+   the plugin root and therefore inside the plugin's SCOPED CSS.
+   `position: fixed` at the viewport origin, zero-sized:
+     - fixed + top/left 0 gives Popper's `position: absolute` children a
+       containing block whose origin matches the viewport coordinates Popper
+       computes (a static container would resolve against whatever positioned
+       ancestor happens to sit above it, offsetting every popper).
+     - zero size means the element itself never covers content or takes clicks;
+       overlays overflow it visibly, as intended.
+     - the z-index matches MUI's `modal` token so overlays clear host chrome
+       (app bar 1100, drawer 1200) from inside the plugin's stacking context.
+   The host's own portal container is deliberately unpositioned ("no overflow/
+   position to avoid stacking context") and can afford to be: it is a direct child
+   of `.gogo-ui`, a sibling of the `relative overflow-hidden` content div. A plugin
+   root sits INSIDE that div, so an unpositioned container here would put every
+   overlay inside an overflow-clipping, positioned ancestor. Hence the difference. */
+.ehx-plugin-root > .ehx-plugin-portal-root {
+  position: fixed;
+  top: 0;
+  left: 0;
+  width: 0;
+  height: 0;
+  z-index: 1300;
+}