Ashley Ryan

Thanks for this @taylor-vann - I no longer work on the project that was having the issue, but I'll pass it on to the team. I did clone the repo...

Figured it out! It was an async timing issue where I was checking for the hidden attribute before the first render was finished. It passes, looks like our workaround can...

This seems to be related to the `position: fixed` set on the host element: https://github.com/vmware-clarity/core/blob/main/projects/core/src/internal-components/popup/popup.element.scss#L34 This is the same logic and css used for overlays like the modal overlay, so...

This is an interesting one. I don't see any special click handler logic in our component, and icons aren't clickable in normal slotted content or in the cds-button-action component. So...

Oh excellent, I was concerned about this checking for safari in the Interactions tab, which I don't want, so thank you for the check for the TestRunner UA. I'll give...

would it be possible to export `defaultPrepare` so that I can call it and then add my own additional awaits? In my case, I need to wait for certain CSS...

Our error boundary component is exactly why I want to be able to skip a story as well. It throws up the webpack veil locally.

Is there any suggestions/recommendations for managing the open/close state as a workaround without `allowsEmptyCollection` (without going fully controlled)? Could we enable `allowsEmptyCollection`, but then override the open behavior ourselves when...

I tried working around the issue by adding another check to the logic to render the popover or not. Instead of `overlayState.isOpen`, I have `overlayState.isOpen && props.items.length > 0`. But...

I spent an hour or two looking at the hook, and slightly tweaked the logic when to open it, but it made about 6 other comboboxes fail, so this doesn't...