{"id":6486,"date":"2018-09-25T18:14:13","date_gmt":"2018-09-25T18:14:13","guid":{"rendered":"http:\/\/putridparrot.com\/blog\/?p=6486"},"modified":"2018-09-25T18:23:32","modified_gmt":"2018-09-25T18:23:32","slug":"starting-out-with-web-components","status":"publish","type":"post","link":"https:\/\/putridparrot.com\/blog\/starting-out-with-web-components\/","title":{"rendered":"Starting out with web components"},"content":{"rendered":"

Introduction<\/strong><\/p>\n

Web components are analogous to self-contained controls or components as you’ll have seen in Windows Forms, WPF etc. They allow developers to package up style, scripts and HTML into a single file which also is used to create a custom element, i.e. not part of the standard HTML.<\/p>\n

Sadly, still not yet available in all browsers (although I believe Polyfills exist for the main ones). Hence, for this post you’ll either need a polyfill or the latest version of Google Chrome (which I’m using to test this with).<\/p>\n

What does it look like using web components?<\/strong><\/p>\n

To start with we create an HTML file for our web component, we then define the template for the component – this is basically the combination of style and the control’s HTML. Finally we write scripts to effect the shadow DOM by interacting with our web component.<\/p>\n

In this post we’re going to create a simple little web component which will flash it’s text. Before we look at the component code let’s see the component in use within the following index.html file<\/p>\n

\r\n<!DOCTYPE html>\r\n<html>\r\n<head>\r\n    <meta charset="utf-8">\r\n    <title>Web Component Test<\/title>\r\n    <link rel="import" href="flashtext.html">\r\n<\/head>\r\n<body>\r\n   <flash-text data-text="Hello World"><\/flash-text>\r\n<\/body>\r\n<\/html>\r\n<\/pre>\n
The key points here are that we include the web component using the line<\/p>\n
\r\n<link rel="import" href="flashtext.html">\r\n<\/pre>\n
and then we use the custom element flash-text<\/em> with it’s custom attributes and we use the component like this<\/p>\n
\r\n<flash-text data-text="Hello World"><\/flash-text>\r\n<\/pre>\n
It’s important<\/strong> to note the closing element, a self closing element is not correctly handled (at least at this time using Google Chrome) and whilst the first usage of a web component might be displayed, if we had several flashing text components in the index.html it’s possible only one would be displayed and no obvious error or reason for the other components not displaying.<\/p>\n
Creating our web component<\/strong><\/p>\n
We already decided our component will be stored in flashtext.html (as that’s what we linked to in the previous section). <\/p>\n
To start off with, create the following<\/p>\n
\r\n<template id="flashTextComponent">\r\n<\/template>\r\n<script>\r\n<\/script>\r\n<\/pre>\n
We’ve created a new template with the id flashTextComponent. This id will be used within our script, it’s not what the pages using the component uses. To create a new custom element by adding the following to the script<\/p>\n
\r\nvar flashText = document.registerElement('flash-text', {\r\n});\r\n<\/pre>\n
But we’re getting a little ahead of ourselves. Let’s instead create some styling and the HTML for our component. Within the template element, place the following<\/p>\n
\r\n<style>\r\n   .flashText {\r\n      float: left;\r\n      width: 152px;\r\n      background-color: red;\r\n      margin-bottom: 20px;\r\n   }\r\n\r\n   .flashText > .text {\r\n      color: #fff;\r\n      font-size: 15px;\r\n      width: 150px;\r\n      text-align: center;\r\n   }\r\n\r\n<\/style>\r\n<div class="flashText">\r\n   <div class="text"><\/div>\r\n<\/div>\r\n<\/pre>\n
The style section simply defines the CSS for both the flashText<\/em> div and the text div within it. The div elements create our layout template. Obviously if you created something like a menu component, the HTML for this would go here with custom attributes which we’ll define next, mapping to the template HTML. <\/p>\n
Next up we need to create the code and custom attributes to map the data to our template. Before we do this let’s make sure the browser supports web components by writing<\/p>\n
\r\nvar template = document.createElement('template');\r\nif('content' in template) {\r\n   \/\/ supports web components\r\n}\r\nelse {\r\n   \/\/ does not support web components\r\n}\r\n<\/pre>\n
If no content<\/em> exists on the template, Google Chrome will report the error in the dev tools stating content is null (or similar wording).<\/p>\n
Within the \/\/ supports web components<\/em> section place the following<\/p>\n
\r\nvar ownerDocument = document.currentScript.ownerDocument;\r\nvar component = ownerDocument.querySelector('#flashTextComponent');\r\n\r\nvar templatePrototype = Object.create(HTMLElement.prototype);\r\n\r\ntemplatePrototype.createdCallback = function () {\r\n   var root = this.createShadowRoot();\r\n   root.appendChild(document.importNode(component.content, true));\r\n\r\n   var name = root.querySelector('.text');\r\n   name.textContent = this.getAttribute('data-text');\r\n\r\n   setInterval(function(){\r\n      name.style.visibility = (name.style.visibility == 'hidden' ? '' : 'hidden');\r\n   }, 1000);\r\n};\r\n\r\nvar flashText = document.registerElement('flash-text', {\r\n    prototype: templatePrototype\r\n});\r\n<\/pre>\n
Let’s look at what we’ve done here. First we get at the ownerDocument<\/em> and then locate our template via it’s id flashTextComponent<\/em>. Now were going to create an HTMLElement prototype which will (in essence) replace our usage of the web component. When the HTMLElement is created we interact with the shadow DOM placing our component HTML into it and then interacting with parts of the template HTML, i.e. in this case placing data from the data-text<\/em> custom attribute, into the text content of the div text<\/em>.<\/p>\n
As we want this text to flash we implement the script for this and attached to the visibility style of the text<\/em>.<\/p>\n
Finally, as mentioned previously, we register our custom element and “map” it to the previously created prototype.<\/p>\n
Using in ASP.NET<\/strong><\/p>\n
ASP.NET can handle static pages easily enough, we just need to add the following to the RouteConfig<\/p>\n
\r\nroutes.IgnoreRoute("{filename}.html");\r\n<\/pre>\n
Now, inside _Layout.cshtml put in the head section<\/p>\n\n
and within the Index.cshtml (or wherever you want it) place your custom elements, i.e.<\/p>\n
\r\n<flash-text data-text="Hello World"><\/flash-text>\r\n<\/pre>\n
References<\/strong><\/p>\n
https:\/\/developer.mozilla.org\/en-US\/docs\/Web\/HTML\/Element\/template<\/a>
\nhttps:\/\/developers.google.com\/web\/fundamentals\/web-components\/customelements<\/a>
\nhttps:\/\/www.webcomponents.org\/<\/a>
\nhttps:\/\/stackoverflow.com\/questions\/45418556\/whats-the-reason-behind-not-allowing-self-closing-tag-in-custom-element-in-spec<\/a><\/p>\n
Code for this post<\/strong><\/p>\n
https:\/\/github.com\/putridparrot\/blog-projects\/tree\/master\/webcomponent<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"
Introduction Web components are analogous to self-contained controls or components as you’ll have seen in Windows Forms, WPF etc. They allow developers to package up style, scripts and HTML into a single file which also is used to create a custom element, i.e. not part of the standard HTML. Sadly, still not yet available in […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[226,45,224,225],"tags":[],"class_list":["post-6486","post","type-post","status-publish","format-standard","hentry","category-html5","category-javascript","category-web","category-web-component"],"jetpack_sharing_enabled":true,"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/posts\/6486","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/comments?post=6486"}],"version-history":[{"count":5,"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/posts\/6486\/revisions"}],"predecessor-version":[{"id":6504,"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/posts\/6486\/revisions\/6504"}],"wp:attachment":[{"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/media?parent=6486"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/categories?post=6486"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/tags?post=6486"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}