Web Components: Where we are now, and what’s next?

@stopsatgreen Web Components: where we are now, and what next?
Responsive Day Out 19/06/15

@stopsatgreen Peter Gasston  @stopsatgreen  broken-links.com

@stopsatgreen For the designers.

@stopsatgreen Web Components have been around for a while.

@stopsatgreen In a trough on the hype cycle.

@stopsatgreen Everybody’s in… but that means trouble.

@stopsatgreen Web Components enable us to create widgets. CSS JS
Widget Widget Widget

@stopsatgreen Composable, reusable, encapsulated. CSS JS Widget Widget Widget

@stopsatgreen We run things, things don’t run we, don’t take
nothing from nobody.

@stopsatgreen React, BEM, etc. are ways of doing this using
the technologies of today.

@stopsatgreen The Extensible Web Manifesto. extensiblewebmanifesto.org <picture> <source srcset="foo.png"  media="(min-width:
600px)"> <img src="bar.png" alt="Logo"> </picture>

@stopsatgreen Web Components are: Templates, HTML Imports, Custom Elements, Shadow
DOM.

@stopsatgreen Templates. Reusable fragments of inert HTML.

@stopsatgreen <script type="text/x-tmpl-mustache"> … </script> <template>…</template>

@stopsatgreen Templates. OK to use, with fallback for IE/Edge.

@stopsatgreen HTML Imports. Include HTML documents in an HTML document.

@stopsatgreen <link rel="import" href="file.html"> // file.js export foo; // page.js
import foo from "file.js";

@stopsatgreen HTML Imports. Will probably be replaced by ES6 modules.

@stopsatgreen Shadow DOM. Hide complex markup inside an element.

@stopsatgreen root = el.createShadowRoot({ mode: 'open' });  root.innerHTML = '<div>…</div>';

@stopsatgreen Shadow DOM is very hard to polyfill.

@stopsatgreen Shadow DOM. Lots still to be defined.

@stopsatgreen Custom Elements. Meaningful markup with bespoke properties.

@stopsatgreen <fun-times></fun-times> document.registerElement('fun-times');

@stopsatgreen <fun-times> = HTMLElement <funtimes> = HTMLUnknownElement document.registerElement('fun-times'); <fun-times> =
fun-times

@stopsatgreen fTs = document.querySelector('fun-times');  fTs.hooray(); p = Object.create(HTMLElement.prototype); p.hooray =
function() {…}; document.registerElement('fun-times',  { prototype: p });

@stopsatgreen // ES6 approach (not final) class fTs extends HTMLElement
{…} document.registerElement('fun-times', fTs); ES6 offers a better way to do this.

@stopsatgreen Custom Elements. Approach is sound, some details to finalise.

@stopsatgreen is A major sticking point.

@stopsatgreen p = Object.create(HTMLButtonElement.prototype); document.registerElement('fun-times', { prototype: p, extends: 'button'
}); <button is="fun-times"></button>

@stopsatgreen is isn’t (probably)

@stopsatgreen In summary: welcome to the trough of disillusionment.

@stopsatgreen A tour of the sausage factory.

@stopsatgreen This is our big opportunity. We need to get
this right.

@stopsatgreen A11y, usability, SEO, etc, become our responsibility.

@stopsatgreen Sturgeon’s Revelation: 90% of everything is crap.

@stopsatgreen The Gold Standard. github.com/webcomponents/gold-standard/wiki

@stopsatgreen Loading, DOM Presence, Content, Interaction, API, Styling, Performance, Localisation,
Factoring, Development.

@stopsatgreen Unix philosophy: every component does one job.

@stopsatgreen Learn a library first, then vanilla.

@stopsatgreen

@stopsatgreen Everybody’s in. but that means trouble. …

@stopsatgreen Cheers.

@stopsatgreen Reading list: • webcomponents.org/articles/why-web-components/ • hacks.mozilla.org/2015/06/the-state-of-web-components/ • aerotwist.com/blog/polymer-for-the-performance-obsessed/ •
tjvantoll.com/speaking/slides/Web-Components-Catch/San-Francisco/ web-components-catch.pdf • w3.org/2015/04/24-webapps-minutes.html • … and many, many more.

Web Components: Where we are now, and what’s next?

Web Components: Where we are now, and what’s next?

More Decks by Peter Gasston

Other Decks in Technology

Featured

Transcript