Web Components

Web Components are a set of features that provide a standard component model for the Web[1] allowing for encapsulation and interoperability of individual HTML elements.

Not to be confused with HTML Components.

Primary technologies used to create them include:[2]

  • 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[3]

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.[4]

Shadow DOM

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.[5][6]

The scoped subtree in an element is called a shadow tree. The element the shadow tree is attached to is called a shadow host.[6]

Shadow DOM must always be connected to an existing element, either through attaching it as a literal element or through scripting. In JavaScript, you attach Shadow DOM to an element using Element.attachShadow().[7]

The ability to scope HTML and CSS is essential to the creation of Custom Elements. If shadow DOM did not exist, different external Custom Elements could interact in unwanted ways.

HTML Template

HTML template is a way to insert chunks of HTML that are stamped at will. The syntax of HTML templates looks like this:

<html>
    <template>
        <h1><slot name="title"></slot></h1>
        <p><slot name="description"></slot></p>
    </template>
</html>

Scripts will not run, and resources that are inside a template will not be fetched until the template is stamped out.[8]

Browser support

Web Components are supported by all major browsers[9].

Backward compatibility with older browsers is implemented using JavaScript-based polyfills.

Libraries

There are several 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 X-Tag, Slim.js, Polymer, Bosonic, Riot.js, and Smart HTML Elements.

Two of these, Bosonic and Polymer, provide ready-made components that are free to use. These components can be used interchangeably as they are all built on open web technologies.[10]

Community

There are numerous community efforts for the Web Components ecosystem. WebComponents.org[11] provides an interface to search for any existing Web Components, Custom Elements Everywhere[12] 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[13] has a dedicated section that shows how those workarounds are used efficiently with example demo apps and similarly related topics.

History

Web Components were introduced by Alex Russell at Fronteers Conference 2011 for the first time.[14]

Polymer, a library based on Web Components was released by Google in 2013.[15]

Firefox 63 adds developer tools support for Web Components.[16]

gollark: It seems vaguely unlikely to me.
gollark: What? I haven't heard of that.
gollark: So if it's before then and I don't lose a bunch of data it would obviously be possible to check such things.
gollark: I can check, I have a closed timelike curve connected to 2103.
gollark: The most interesting quantum thingy™ I'm aware of is Grover's algorithm, which seems to just magically be able to speed up some search-ish/brute-force things using magic.

References
  1. GitHub - w3c/webcomponents: Web Components specifications., World Wide Web Consortium, 2019-01-03, retrieved 2019-01-03
  2. "Web Components". MDN Web Docs. Retrieved 2019-01-03.
  3. "<template>: The Content Template element". MDN Web Docs. Mozilla. Retrieved 2018-07-08.
  4. "Custom Elements". www.w3.org. Retrieved 2016-12-01.
  5. "What the Heck is Shadow DOM?". Dimitri Glazkov. 2011-01-15. Retrieved 2016-12-01.
  6. "Shadow DOM v1: Self-Contained Web Components | Web | Google Developers". Google Developers. Retrieved 2016-12-01.
  7. "Shadow DOM". Mozilla Developer Network. Retrieved 2016-12-01.
  8. Community. "Introduction to the template elements — WebComponents.org". webcomponents.org. Retrieved 2016-12-03.
  9. "webcomponents.org - Discuss & share web components". www.webcomponents.org. Retrieved 2020-07-22.
  10. "Web Components in production use – are we there yet?". vaadin.com. Retrieved 2016-11-21.
  11. "Search available Web Components".
  12. "Validate Front-end Frameworks with Web Components Standard".
  13. "Web Components Tutorials".
  14. "Web Components and Model Driven Views by Alex Russell · Fronteers". fronteers.nl. Retrieved 2016-12-02.
  15. "The state of Web Components ★ Mozilla Hacks – the Web developer blog". hacks.mozilla.org. Retrieved 2016-12-02.
  16. "Developer Tools support for Web Components in Firefox 63".
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.