Cee Chen

Hey hey, I'm super super sorry y'all (especially for the very slow response). I can definitely reproduce the issue you're seeing (even on modern browsers) by trying to set a...

Ahh man, that's a great question. I definitely see the use case especially for applications using JS frameworks like React, etc., where they're gonna have to manually call `objectFitPolyfill()` anyway,...

Hey hey! Quick question - what's the specific use-case for non-visible elements? I can think of 2 off the top of my head (lazy-loading and carousels) - but I'm not...

Heya MasGaNo! First of all, this is really cool, and I'm impressed that you did so much work on this! I definitely don't think it's a bad idea, but I...

Hey @MasGaNo! Just wanted to apologize for how long it's taken to get back to you on your PRs - I've been super swamped with side work, but I promise...

I'm not 100% seeing the issue here. When you type to start searching and select what you've searched for, the search does clear and therefore the onSearchChange callback is valid:...

Ahhh, I see that UX confusion especially with how single selection displays plain text selections vs user search. To be honest I still think the `''` case is very obviously...

It's not that the user is searching after selection, it's that we're reporting whenever the value of the search text changes, even when EUI is programmatically clearing it. So perhaps...

Looks like it _may_ possibly be a cross browser input rendering issue? Do you mind specifying your OS and browser?

No worries! I'm on FF 101.0.1 on macOS 11.6 and the CodeSandbox that Caroline linked is fine for me. My best guess is that there may be some custom CSS...