webcomponents.js
npm install @mstyk/webcomponents.jswebcomponents.js
================

A suite of polyfills supporting the Web Components specs:
Custom Elements: allows authors to define their own custom tags (spec).
HTML Imports: a way to include and reuse HTML documents via other HTML documents (spec).
Shadow DOM: provides encapsulation by hiding DOM subtrees under shadow roots (spec).
This also folds in polyfills for MutationObserver and WeakMap.
Pre-built (concatenated & minified) versions of the polyfills are maintained in the tagged versions of this repo. There are two variants:
webcomponents.js includes all of the polyfills.
webcomponents-lite.js includes all polyfills except for shadow DOM.
Our polyfills are intended to work in the latest versions of evergreen browsers. See below
for our complete browser support matrix:
| Polyfill | IE10 | IE11+ | Chrome | Firefox | Safari 7+ | Chrome Android | Mobile Safari* |
| ---------- |:----:|:-----:|:-------:|:--------:|:----------:|:---------------:|:--------------:|
| Custom Elements | ~ | ✓ | ✓ | ✓ | ✓ | ✓| ✓ |
| HTML Imports | ~ | ✓ | ✓ | ✓ | ✓| ✓| ✓ |
| Shadow DOM | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Templates | ✓ | ✓ | ✓ | ✓| ✓ | ✓ | ✓ |
*Indicates the current version of the browser
~Indicates support may be flaky. If using Custom Elements or HTML Imports with Shadow DOM,
you will get the non-flaky Mutation Observer polyfill that Shadow DOM includes.
The polyfills may work in older browsers, however require additional polyfills (such as classList)
to be used. We cannot guarantee support for browsers outside of our compatibility matrix.
If you wish to build the polyfills yourself, you'll need node and gulp on your system:
* install node.js using the instructions on their website
* use npm to install gulp.js: npm install -g gulp
Now you are ready to build the polyfills with:
# install dependencies
npm install
# build
gulp build
The builds will be placed into the dist/ directory.
See the contributing guide
Everything in this repository is BSD style license unless otherwise specified.
Copyright (c) 2015 The Polymer Authors. All rights reserved.
Under native HTML Imports, tags in the main document block the loading of such imports. This is to ensure the imports have loaded and any registered elements in them have been upgraded.
The webcomponents.js and webcomponents-lite.js polyfills parse element definitions and handle their upgrade asynchronously. If prematurely fetching the element from the DOM before it has an opportunity to upgrade, you'll be working with an HTMLUnknownElement.
For these situations (or when you need an approximate replacement for the Polymer 0.5 polymer-ready behavior), you can use the WebComponentsReady event as a signal before interacting with the element. The criteria for this event to fire is all Custom Elements with definitions registered by the time HTML Imports available at load time have loaded have upgraded.
``js`
window.addEventListener('WebComponentsReady', function(e) {
// imports are loaded and elements have been registered
console.log('Components are ready');
});
* Limited CSS encapsulation
* Element wrapping / unwrapping limitations
* Custom element's constructor property is unreliable
* Contenteditable elements do not trigger MutationObserver
* ShadowCSS: :host-context(...):host(...) doesn't work
* ShadowCSS: :host(.zot:not(.bar:nth-child(2))) doesn't work
* HTML imports: document.currentScript doesn't work as expected
* execCommand isn't supported under Shadow DOM
The Shadow DOM polyfill can't prevent document styles from leaking into shadow roots. It can, however, encapsulate styles within shadow roots to some extent. This behavior isn't automatically emulated by the Shadow DOM polyfill, but it can be achieved by manually using the included ShadowCSS shim:
``
WebComponents.ShadowCSS.shimStyling( shadowRoot, scope );
... where shadowRoot is the shadow root of a DOM element, and scope is the name of the scope used to prefix the selectors. This removes all