Skip to content

fix(Combobox): let the menu drop shadow render in prod (MET-3088) - #65

Merged
Zayooo00 merged 1 commit into
mainfrom
fix/combobox-menu-shadow-clip
Sep 1, 2026
Merged

fix(Combobox): let the menu drop shadow render in prod (MET-3088)#65
Zayooo00 merged 1 commit into
mainfrom
fix/combobox-menu-shadow-clip

Conversation

@Zayooo00

@Zayooo00 Zayooo00 commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

Follow-up to #62#64. On the deployed app the Combobox menu rendered with no drop shadow even though one is set via optionsClassName (0 4px 48px #00000080). Two things clipped it:

1. .options clip-path: inset(0 -48px -48px -48px) — a leftover from when the menu was an absolutely-positioned sibling right below the input, to stop its shadow bleeding up over the input. It cut the shadow off flush at the top and to nothing on the other sides. Moved into the canvas-only branch (inline clipPath), where the menu is still inline + flush under the input and the clip is still wanted. In prod (portalled + gapped) it's gone.

2. overflow: auto on .positioner — Headless UI's Floating UI size middleware stamps overflow: auto + max-width/max-height inline on the portal root every reposition. That scroll box clips the inner .options shadow. Overridden back to overflow: visible !important; the inner .options keeps its own max-height: 494px + overflow-y: auto so long lists still scroll.

Canvas behaviour unchanged.

next lint, tsc, vitest (49) green.

@notion-workspace

Copy link
Copy Markdown

@Zayooo00
Zayooo00 force-pushed the fix/combobox-menu-shadow-clip branch from b9f4812 to f9bfe4e Compare September 1, 2026 07:42
@Zayooo00 Zayooo00 changed the title fix(Combobox): drop menu clip-path so the drop shadow renders (MET-3088) fix(Combobox): drop menu clip-path in prod so the drop shadow renders (MET-3088) Sep 1, 2026
Two things were clipping the box shadow (set via `optionsClassName`,
`0 4px 48px`) on the deployed menu:

- `.options` had `clip-path: inset(0 -48px -48px -48px)` - a leftover from
  when the menu was an absolutely positioned sibling right below the input
  and its shadow could bleed up over it. Moved into the canvas-only branch
  (inline), where the menu is still inline and flush under the input; in
  prod (portalled + gapped) the clip is gone.

- Headless UI's Floating UI `size` middleware stamps `overflow: auto`
  inline on `.positioner` (the portal root), whose scroll box clips the
  inner `.options` shadow. Override it back to `overflow: visible`; the
  inner `.options` keeps its own `max-height` + `overflow-y` so long
  lists still scroll.

Canvas behaviour unchanged.
@Zayooo00
Zayooo00 force-pushed the fix/combobox-menu-shadow-clip branch from f9bfe4e to d76ba70 Compare September 1, 2026 07:44
@Zayooo00 Zayooo00 changed the title fix(Combobox): drop menu clip-path in prod so the drop shadow renders (MET-3088) fix(Combobox): let the menu drop shadow render in prod (MET-3088) Sep 1, 2026
@Zayooo00
Zayooo00 merged commit 8be486b into main Sep 1, 2026
2 checks passed
@Zayooo00
Zayooo00 deleted the fix/combobox-menu-shadow-clip branch September 1, 2026 07:50
Zayooo00 added a commit to myevaluations/myevals-plasmic-utils that referenced this pull request Sep 1, 2026
…llstackhouse#65) (#7)

Two things were clipping the box shadow (set via `optionsClassName`,
`0 4px 48px`) on the deployed menu:

- `.options` had `clip-path: inset(0 -48px -48px -48px)` - a leftover from
  when the menu was an absolutely positioned sibling right below the input
  and its shadow could bleed up over it. Moved into the canvas-only branch
  (inline), where the menu is still inline and flush under the input; in
  prod (portalled + gapped) the clip is gone.

- Headless UI's Floating UI `size` middleware stamps `overflow: auto`
  inline on `.positioner` (the portal root), whose scroll box clips the
  inner `.options` shadow. Override it back to `overflow: visible`; the
  inner `.options` keeps its own `max-height` + `overflow-y` so long
  lists still scroll.

Canvas behaviour unchanged.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants