silverwind

Sure, what can be done with CSS only should be done with it. But I'm really talking about the more complex components like Dropdown and Modal which will require JS.

Did not try it yet, but first we should assert that the a11y of these components is ok. We should not blindly trust their claims 😆.

@wxiaoguang maybe you can review these components for their accessibility: - https://shoelace.style/components/dropdown - https://shoelace.style/components/select - https://shoelace.style/components/menu - https://shoelace.style/components/dialog

I'm skeptical, seen too many such takeovers go wrong. I guess we'll wait until it's clear which components will be part of their "pro" version. Also I would like to...

Seems okay. Basic components will remain in the free version and those are all we need. We definitely don't need things like data grid. Of course we should remain on...

> there are ways to implement dropdown and modal without JS Only the very simplest of dropdowns can. As soon as you need functionality like a search you are in...

No further progress on this, but at least Fomantic needs to go eventually, e.g. the dropdowns mostly. As for Vue vs. Webcomponents: Yes we can keep using Vue, but one...

Ah, I wasn't aware that Vue components can render as custom elements. This could possibly be useful to avoid "pop in" if those components are then loaded in the webcomponents...

https://github.com/floating-ui/floating-ui is a low-level library for floating elements and it could be used to replace both our tippy.js usage as well as the fomantic dropdowns. It's definitely not as high-level...

What we should do is at time of creation of the commit or creation/edit of a comment containing issue refs, check if the referenced issue exists, and if it does...