Custom Elements

To quote the Google primer on Custom Elements:

With Custom Elements, web developers can create new HTML tags, beef-up existing HTML tags, or extend the components other developers have authored. The API is the foundation of web components. It brings a web standards-based way to create reusable components using nothing more than vanilla JS/HTML/CSS. The result is less code, modular code, and more reuse in our apps.

We highly recommend reading through the full Custom Elements primer on Google’s Web Fundamentals.

By default, to provide sufficient cross-browser support for custom elements, Flynt implements a polyfill within the DocumentDefault component.

The is attribute

In the view template, the is attribute is used to declare a component as a custom element. This means we are able to extend native HTML elements (read more about this here). We are also able to use this attribute to scope our component styles.

<div is="flynt-example-component" class="flyntComponent">
  <p>This Example Component has an `is` attribute.</p>

Custom Elements Template

A basic custom elements script could look like this:

class ExampleComponent extends window.HTMLDivElement {
  constructor (self) {
    self = super(self)
    self.$ = $(self)
    return self

  resolveElements () {
    this.$content = $('.exampleComponent-content', this)

  connectedCallback () {
    this.$.on('click', '.exampleComponent-button', this.openContent)

  openContent = (e) => {

window.customElements.define('flynt-example-component', ExampleComponent, {extends: 'div'})