Krisztian Horvath

**EDIT:** I've added a line to bump Storybook to its latest version. (Original sample was still at BETA 5.) You may want to use the https format of the repo:...

Updated the workaround to use a utility function that recursively discovers `styles` of child components. This makes it simpler to use. That said the vue-loader doing this automatically would still...

Until resolved, here is a workaround and minimal reproduction: ```js class TheProblem extends HTMLElement { constructor() { super(); this.role = 'switch'; } } class AWorkaround extends TheProblem { constructor() {...

I've looked into the PoC and love that it keeps the content right where it was put. Vue for instance is sensitive to its rendered elements getting relocated especially when...

Seemingly not Vue or React issue. On Chrome, the error is triggered by code as simple as: ```js import { LionSwitch } from '@lion/switch'; customElements.define('lion-switch', LionSwitch); const el = document.createElement('lion-switch');...

Upon further investigation, this issue is related to #1740 but both setting the `role` and the `checked` in the constructor cause the component to break. Unfortunately, simply disabling the setter...

Created PR in which I've addressed the form-core mixins in this manner. Assumed it'd be a patch release.

Found a workaround: declare a fake class intended only to be documented with JSDoc. This way the analyzer will ignore the real class as it has no `@element` annotation.

Hi! Can't wait! 😁

@tlouisse I took the dialog for a spin. It works well in the LionDialog! Unfortunately, when testing out the LionSelectRich the component seems to be broken in the 0.0.11 version....