Steven Orvell
68ef957139
Adds a window.WebComponents global. Existence of this global indicates that the WebComponentsReady event will be fired when polyfills are ready. After the event fires WebComonents.ready is set to true. This enables testing environments like web-component-tester to more easily determine if they should wait for the WebComponentsReady event before starting.
2017-04-24 12:39:37 -07:00
Daniel Freedman
b3643c7fe3
set webComponentsReady flag on script when WebComponentsReady event is fired
2017-04-21 17:54:38 -07:00
Steven Orvell
b1b6dbd4f9
[ci-skip] Fix comments
2017-04-19 18:45:38 -07:00
Steven Orvell
4edc015356
Correct note about CSP. document.write does not violate CSP.
2017-04-19 15:47:12 -07:00
Steven Orvell
834e18dd82
Remove stub of HTMLImports as this makes any test for whenReady that does window.HTMLImports && HTMLImports.whenReady fail. [Note: this may require an update to WCT.]
2017-04-18 16:51:16 -07:00
Steven Orvell
437da91a8c
* Load full suite of polyfills (-lite) if ES6 features (e.g. Array.from) are not available. We do this because if ES6 is not available, none of the other webcomponents features (which require ES6) are definitely not available.
...
* Uses `document.write` to load polyfills if and only if native HTML imports exists (older Chrome browsers). This ensures that polyfills are loaded by the time scripts in HTML imports run.
* Adds old Chrome version to test matrix.
2017-04-18 16:01:34 -07:00
Daniel Freedman
7b13afd170
Make WebComponentsReady fire consistently for Chrome
...
Also fire WebComponentsReady on document and have it bubble for
backwards compatibility
Fixes #753
Fixes #756
2017-04-06 17:01:05 -07:00
valdrinkoshi
79fe34ba80
stub HTMLImports
2017-03-22 11:10:01 -07:00
Daniel Freedman
d16447a82a
Cleanup README
...
Fix es5 loader by checking for the correct name :P
2017-03-06 14:43:58 -08:00
Daniel Freedman
20e23374b9
Make bundles with the Custom Elements es5 compatibility shim
...
Fixes #710
Also, fix loaders to be compatible with ES5-only browsers
Fixes #706
2017-03-06 11:46:12 -08:00
Steven Orvell
acf8eaf747
loader: (1) avoid native ShadowDOM when getRootNode is unavailable; (2) include template polyfill when documentFragment cloning is broken
2017-02-24 12:09:06 -08:00
Monica Dinculescu
05bc9b7ae6
dan review
2017-02-22 13:57:21 -08:00
Daniel Freedman
8cf4a45385
simplify no-polyfill case
2017-02-16 14:49:19 -08:00
Daniel Freedman
bf447dfc9c
remove todo
2017-02-16 12:51:45 -08:00
Daniel Freedman
0dbc9e7536
remove webcomponents-none, only load scopingshim when needed
2017-02-16 12:21:24 -08:00
valdrinkoshi
2918670bcd
remove HTMLImports stub
2017-02-14 17:41:33 -08:00
valdrinkoshi
6c53a012b9
conditional stubbing of HTMLImports
2017-02-14 15:10:09 -08:00
valdrinkoshi
1bd7090b73
WebComponentsReady fired once.
2017-02-14 14:05:44 -08:00
Steven Orvell
1a9569ca95
Add clarity to comments. Remove unresolved from the "none" case since it should not be needed.
2017-02-06 11:26:51 -08:00
Steven Orvell
1bea1ac000
Always load shadydom first and then custom-elements.
...
Temporarily change bower to use shadydom#prototype-importNode branch.
2017-02-01 11:23:15 -08:00
valdrinkoshi
b12a6376b3
stub HTMLImports.useNative, try latest hi and ce
2017-01-27 15:38:20 -08:00
Monica Dinculescu
a7d2aae2c3
update bundles
2017-01-17 15:16:28 -08:00
Monica Dinculescu
824c1e4882
update loader; update tests to use loader
2017-01-12 17:11:41 -08:00
