Customs Elements is what would make me quite happy with UI design on the browser side.
Now just have to wait a few years to be able to use it, or hope the polyfills actually cover all the browsers versions we might need to target.
Custom Elements v1: Reusable Web Components
11–20 of 41 posts
Re: Custom Elements v1: Reusable Web Components
#12You can use custom elements also in golang :)
Re: Custom Elements v1: Reusable Web Components
#13please correct me if I'm wrong but it seems that custom elements still do nothing about dependency hell (it's not possible to use same lib in different versions)
Re: Custom Elements v1: Reusable Web Components
#14could it replace React ?
Re: Custom Elements v1: Reusable Web Components
#15Components with extensibility through inheritance written in a prototype-based language. Having worked with around a dozen component-based systems over the years I'm not particularly enthusiastic.
I think it would be much better for the web if browsers had a sane API for extending behaviors of any tag via attributes. This would make things easily composable and eliminate most problems of traditional component-based systems.
Edit: And yes, I'm aware of is="" functionality. It's not exactly what I'm talking about. In fact, if the specs were designed the way I mentioned, there would be no need for making anything special for built-in elements as opposed to the new ones.
Re: Custom Elements v1: Reusable Web Components
#16This is the kicker for me:
> At time of writing, no browser has implemented customized built-in elements. Chrome plans to implement them (status) but other browsers have expressed distaste for implementing the is="" syntax.
I would love to just be able to "fix" the normalization around several built-in elements.
Re: Custom Elements v1: Reusable Web Components
#17could it replace React ?
We've been using Web Components + Virtual DOM to build our web apps for the last year at Mixpanel: https://github.com/mixpanel/panel. The biggest issues have been dealing with polyfill issues (especially Shadow DOM leakage) and versioning elements (given the global namespace issue of "registerElement")
Re: Custom Elements v1: Reusable Web Components
#18Is it possible to nest custom elements? I suppose it should be, but how would it be seen in DOM?
How can I get notifications in my-container when someone from outside adds another child to it?
Re: Custom Elements v1: Reusable Web Components
#19please correct me if I'm wrong but it seems that custom elements still do nothing about dependency hell (it's not possible to use same lib in different versions)
Why would they be expected to?
Re: Custom Elements v1: Reusable Web Components
#20Components with extensibility through inheritance written in a prototype-based language. Having worked with around a dozen component-based systems over the years I'm not particularly enthusiastic. I think it would be much better for the web if browsers had a sane API for extending behaviors of any tag via attributes. This would make things easily composable and eliminate most problems of traditional component-based s…
> It would be even better if people working on these specs spent some time reading research papers on how a sane component-based system could work.
I don't know the people working on these specs, but presuming that they aren't aware of research in the area, and moreover of what has worked in practice and what hasn't, is audacious.