<flex-box></flex-box>
with css into a re-usable css framework type deal. I'm wondering if there's some sort of catch when it comes to browser compatibility or something else?
How should web components look like, if my html looks like this
graph-tree>
<graph-tree-item label="Item 1">
<graph-tree-item label="Item 1-1">
<graph-tree-item label="Item 1-1-1"></graph-tree-item>
</graph-tree-item>
</graph-tree-item>
</graph-tree>
Web Components work just like other HTML elements, except that they work on any website with the help of Shadow DOM.
Hi everyone! I'm a developer for a company called ZingSoft. We have a product called ZingGrid which is a commercial grid web component. The code is closed source (https://github.com/ZingGrid/zinggrid) but available for free use in commercial products. How does we fit into the web component community and if we belong on this platform?
I'm not trying to be spam or promotion, we are deeply involved and invested in web components and am wondering your thoughts on:
- commercial web components being available on webcomponents.org
- commercial web components in general. Is there a place for them for you? What would you expect
Make it open-source :)
Hi all, long time fan of web components here. Have been working on a side project for a material design ui component library. I have slowly been working on it over the last 2 years and am finally going to start using it for some projects. I would love to get some feedback on it. Here is a link to the github and to the doc website. There are still some components under development and some others on the road map, but all the basics plus some are there. One big thing to note is the focus on mobile and desktop compatibly (the components are design to work with both and have specific features based on the view)
https://github.com/webformula/pax-components
http://components.webformula.io/
eg:
Custom Elements specification points to:
https://w3c.github.io/webcomponents/spec/custom/