The Case for Custom Elements: Part 2
Rob Dodson
31412

> If each library creates its own wrappers, with their own APIs, then there’s no way other libraries will be able to consume those components.

Wouldn’t this be true for custom elements too since custom elements are just JavaScript?

Will there be some type of validation for Custom Elements similar to AMP validation? Could you imagine trying to interop with external elements, some of which use html imports, some of which use a single file, all of which use a different DOM library or different versions of the same library (e.g. deps on mustache, handlebars, preact, etc)? My gut feeling is that creating contrived examples of fancy-button and my-new-element is easy, but in reality many developers will copy code from somewhere into their app and we’re back to jQuery plugins.

Like what you read? Give kevinw88 a round of applause.

From a quick cheer to a standing ovation, clap to show how much you enjoyed this story.