Web Components
{{Short description|Software}}
{{distinguish|HTML Components}}
{{multiple issues|
{{original research|date=June 2021}}
{{notability|date=June 2021}}
}}
Web Components are a set of features that provide a standard component model for the web{{Citation|title=GitHub - w3c/webcomponents: Web Components specifications.|date=2019-01-03|url=https://github.com/w3c/webcomponents|publisher=World Wide Web Consortium|access-date=2019-01-03}} allowing for encapsulation and interoperability of individual HTML elements. Web Components are a popular approach when building microfrontends.
Primary technologies used to create Web Components include:{{Cite web|url=https://developer.mozilla.org/en-US/docs/Web/Web_Components|title=Web Components|website=MDN Web Docs|access-date=2019-01-03}}
; Custom Elements
: APIs to define new HTML elements
; Shadow DOM
: encapsulated DOM and styling, with composition
; HTML Templates
: HTML fragments that are not rendered, but stored until instantiated via JavaScript{{cite web |url=https://developer.mozilla.org/en-US/docs/Web/HTML/Element/template |title=
|website=MDN Web Docs |publisher=Mozilla |access-date=2018-07-08}}
Features
= Custom Elements=
There are two parts to Custom Elements: autonomous custom elements and customized built-in elements. Autonomous custom elements are HTML elements that are entirely separated from native HTML elements; they are essentially built from the bottom up using the Custom Elements API. Customized built-in elements are elements that are built upon native HTML elements to reuse their functionality.{{Cite web|url=https://www.w3.org/TR/custom-elements/|title=Custom Elements|website=www.w3.org|access-date=2016-12-01}}
= Shadow DOM =
The Shadow DOM is a functionality that allows the web browser to render DOM elements without putting them into the main document DOM tree. This creates a barrier between what the developer and the browser can reach; the developer cannot access the Shadow DOM in the same way they would with nested elements, while the browser can render and modify that code the same way it would with nested elements. The impact of CSS scoped within the Shadow DOM of a particular element is that HTML elements can be encapsulated without the risk of CSS styles leaking and affecting elements that they were not supposed to affect. Although these elements are encapsulated with regard to HTML and CSS, they can still fire events that can be picked up by other elements in the document.{{Cite web|url=https://glazkov.com/2011/01/14/what-the-heck-is-shadow-dom/|title=What the Heck is Shadow DOM?|date=2011-01-15|website=Dimitri Glazkov|access-date=2016-12-01}}{{Cite web|url=https://developers.google.com/web/fundamentals/getting-started/primers/shadowdom|title=Shadow DOM v1: Self-Contained Web Components {{!}} Web {{!}} Google Developers|website=Google Developers|access-date=2016-12-01}}
The scoped subtree in an element is called a shadow tree. The element the shadow tree is attached to is called a shadow host.
A Shadow DOM must always be connected to an existing element, either through attaching it as a literal element or through scripting. In JavaScript, Shadow DOMs are attached to an element using Element.attachShadow().{{Cite web|url=https://developer.mozilla.org/en-US/docs/Web/Web_Components/Shadow_DOM|title=Shadow DOM|website=Mozilla Developer Network|access-date=2016-12-01}}
= HTML Template =
A HTML template is a way to insert chunks of HTML that are cloned from the template at will. The syntax of HTML templates looks like this:
Scripts will not run, and resources that are inside a template will not be fetched until the template is instantiated.{{Cite web|url=http://webcomponents.org/articles/introduction-to-template-element/|title=Introduction to the template elements — WebComponents.org|last=Community|website=webcomponents.org|access-date=2016-12-03}}
Browser support
Web Components are supported by current versions of all major browsers.{{Cite web|title=webcomponents.org - Discuss & share web components|url=https://www.webcomponents.org/|access-date=2020-07-22|website=www.webcomponents.org|language=en-us}}
Backward compatibility with older browsers is implemented using JavaScript-based polyfills.
Libraries
There are many libraries that are built on Web Components with the aim of increasing the level of abstraction when creating custom elements. Some of these libraries are [https://x-tag.github.io/ X-Tag], [https://slimjs.com/ Slim.js], Polymer, [https://bosonic.github.io/ Bosonic], [https://riot.js.org/ Riot.js], [https://developer.salesforce.com/docs/component-library/documentation/en/lwc Salesforce Lightning Web Components], [https://www.dataformsjs.com/ DataFormsJS], [https://github.com/telepathic-elements/telepathic-element/ Telepathy], and [https://wompo.dev Wompo]
Community
There are numerous community efforts for the Web Components ecosystem. [https://www.webcomponents.org/ WebComponents.org]{{Cite web|url=https://www.webcomponents.org/search|title=Search available Web Components}} provides an interface to search for any existing Web Components, Custom Elements Everywhere{{Cite web|url=https://custom-elements-everywhere.com|title=Validate Front-end Frameworks with Web Components Standard}} validates whether popular front-end frameworks are compatible and ready to use Web Components standard, with a set of pending bugs and available workarounds. Moreover, Vaadin Tutorials{{Cite web|url=https://vaadin.com/learn/tutorials?query=web%20components|title=Web Components Tutorials}} has a dedicated section that shows how those workarounds are used efficiently with example demo apps and similarly related topics aka Infinite Craft
History
In 2011, Web Components were introduced for the first time by Alex Russell at Fronteers Conference.{{Cite web|url=https://fronteers.nl/congres/2011/sessions/web-components-and-model-driven-views-alex-russell|title=Web Components and Model Driven Views by Alex Russell · Fronteers|website=fronteers.nl|access-date=2016-12-02}}
In 2013, Polymer, a library based on Web Components was released by Google. Polymer is canonical implementation of Material Design for web application user interfaces.
In 2016, RequireJS was introduced as JavaScript library and AMD loader plugin for custom elements.{{cite web|url=https://developer.adobe.com/commerce/frontend-core/javascript/requirejs/|title=RequireJS in Commerce}}
In 2017, Ionic (mobile app framework) team built StencilJS, a JavaScript compiler that generates Web Components.{{cite web|url=https://levelup.gitconnected.com/web-component-solutions-a-comparison-e2fa25c34730|title=Web Component Solutions: A Comparison}}
In 2018, Angular 6 introduced Angular Elements that lets you package your Angular components as custom web elements, which are part of the web components set of web platform APIs.{{cite web|url=https://www.freecodecamp.org/news/how-to-create-angular-6-custom-elements-web-components-c88814dc6e0a/|title=How to create Angular 6 Custom Elements and Web Components}}
In 2018, Firefox 63 enabled Web Components support by default and updated the developer tools to support them.{{Cite web | url=https://blog.nightly.mozilla.org/2018/09/06/developer-tools-support-for-web-components-in-firefox-63/ |title = Developer Tools support for Web Components in Firefox 63}}
In 2018, LitElement was developed by the Google Chrome team as part of larger Polymer project. LitElement was designed to be a lightweight and easy-to-use framework for creating web components.