Ashley Ryan

I've been looking into workarounds on our side some more and it looks like React will actually handle this properly in React 19 once they release the proper web component...

In our case, the issue was that we had a CSS selector on `[hidden]` that hid the element. We were able to work around the issue by handling the false...

With React 18 [adding support for web components behind the experimental flag](https://github.com/facebook/react/issues/11347#issuecomment-988970952), I'm wondering if testing-library has given any more thought to officially supporting the shadow dom. @Westbrook has done...

clarity-ng has a dependency on Core and not the other way around, so Core is never going to care about NG's z-indexes. HOWEVER, I think Core has it's own positioning...

This may be related to this issue: https://github.com/vmware-clarity/core/issues/61 I might have a fix for icons, and then I'll check the other elements as well.

Hello, can you please create a working example of the issue you're describing here: https://stackblitz.com/@clr-team/

If I'm following your script correctly, I should: 1. Go to https://angular.clarity.design/documentation/tabs 2. Scroll down to the Tab Overflow example and select the first tab 3. Click the overflow button...

In v6, the ControlAction was refactored to be derived from the new ButtonAction element. Part of that work introduced an absolute positioned touch target on top of the action button...

We need to get @colinreedmiller involved since this includes a visual change (and a slightly breaking one at that)

@colinreedmiller this PR came out of this discussion - I think it's a visual breaking change based on the screenshot? https://github.com/vmware-clarity/ng-clarity/discussions/225