Ardeshir Izadi

Thanks for the workaround @mihkeleidast 👍 It indeed works. And I also don't understand why its needed 🤷

I looked into this for a few hours: - It is hard to reproduce it in the automated tests for some reason. But it is easily reproducible in the context...

I found about the reason that prevented me from writing a test for this bug: https://github.com/ing-bank/lion/issues/2351 After fixing https://github.com/ing-bank/lion/issues/2351, I should be unblocked for working on this bug with disabled...

This PR: https://github.com/ing-bank/lion/pull/2354 fixes this issue

Thanks. I've also created this reproduction link in my other issue: https://studio.webcomponents.dev/edit/CdTHK8iuVNqVSuive1NH/src/index.js?p=README.md that shows the difference in behavior for lion button vs native button

Note that Chromium and Firefox behave differently about native autocomplete. Suppose this example: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/select On chromium, open select box, type "cat" (or any option present), so the option would be...

This is my ugly workaround: ```ts const lastHighlightedItem = React.useRef({ value: null, }); const onHighlightChange = React.useCallback(function(_event, item, reason) { if (reason !== 'mouse') lastHighlightedItem.current.value = item; }, []); const...

This PR: https://github.com/ing-bank/lion/pull/2353 should fix this issue

@pauldavisthefirst thanks for the quick response. But as I mentioned, Ardour manual is the only website that I find hard reading. The fonts are thin. I don't have weak eyesight...

I have the same problem. It causes my app to break resolving some packages. ``` $ pnpm -v 9.0.0 $ pnpm -C test -v 9.0.0 $ cd test test$ pnpm...