I know there are workarounds for this issue mentioned multiple times in other questions (see list). But replacing click for pointerdown is not always a good solution, as some interfaces need pointerup events to work separately from the click/down events, not just for CSS reasons, but for more advanced logical ones too.
I’d like to understand if this is a by-design limitation of both features working together, or if we should open an issue for this in the repo so it gets attention eventually.
If there are any workaround for that as well not yet mentioned in other answers, which works for separate pointer up/down events, we’d be very grateful to know.
Thanks for the attention.