Shoelace: A library of web components
shoelace.style
Shoelace: A library of web components
1–10 of 114 posts
Re: Shoelace: A library of web components
#2On my phone, the whole page is covered by the left side menu. Tapping on the burger doesn’t hide the menu either. Not a good impression from a web design library.
Re: Shoelace: A library of web components
#3On my phone, the whole page is covered by the left side menu. Tapping on the burger doesn’t hide the menu either. Not a good impression from a web design library.
What phone are you using? It seems fine on my old iPhone mini.
Re: Shoelace: A library of web components
#4Re: Shoelace: A library of web components
#5I've used these in the past and they are really well done.
Also the developer now works at Microsoft and they are using it so at least it has a major backer.
Re: Shoelace: A library of web components
#6These look and feel great! Will give it a try.
Re: Shoelace: A library of web components
#7this looks great. I'm puzzled by something though: why does it duplicate components that already exist in standard HTML5 (Button, Checkbox, Dropdown etc.)? The whole idea of web components is being able to augment what's already built in, not have to replace it.
Maybe it's for consistency (styling/behaviour). Either way, it looks really well done.
Re: Shoelace: A library of web components
#8this looks great. I'm puzzled by something though: why does it duplicate components that already exist in standard HTML5 (Button, Checkbox, Dropdown etc.)? The whole idea of web components is being able to augment what's already built in, not have to replace it. Maybe it's for consistency (styling/behaviour). Either way, it looks really well done.
Theming is at least one reason.
Re: Shoelace: A library of web components
#9I've used this, works great.
Good option for those who prefer vanilla web components.
Only hangup I ran into was the event/callback based API for some components - promises would have been more convenient.
Re: Shoelace: A library of web components
#10this looks great. I'm puzzled by something though: why does it duplicate components that already exist in standard HTML5 (Button, Checkbox, Dropdown etc.)? The whole idea of web components is being able to augment what's already built in, not have to replace it. Maybe it's for consistency (styling/behaviour). Either way, it looks really well done.
Because browsers offer very little styling and customization options even for the handful of built-in elements. That's why every library under the sun tries to re-invent them again, and again, and again.
https://open-ui.org/ will finally help with this, but it's a very slow process.