Releases: corpusculejs/custom-builtin-elements
v0.3.0
An important release that fixes a couple of severe bugs that existed in earlier versions.
The first bug was connected with incorrect tag registering, which resulted in a situation when any element created with this polyfill had the UNDEFINED tag name, which is entirely wrong.
The second bug was less harmful and was that the overridden whenDefined method didn't follow the specification. It didn't correctly wait for the element definition, which could break the correct code that works in browsers that implement this feature.
v0.2.0
This release provides some improvements of the polyfill usage.
First of all, it is no necessary to create minimal implementation of customElements registry by hands. Now the polyfill provides it as a separate module, so you can just import it. Or you still can use another implementation of the customElements registry like @webcomponents/webcomponentsjs polyfill.
The separate module shape was chosen to reduce the amount of code that should be shipped to users who already have built-in customElements or use any of web components polyfill.
You can import minimal implementation in different ways. Just note that it should be executed before the main polyfill because the polyfill overrides the already existing methods. It is true for any of web components polyfills: they should go before this polyfill.
Examples of importing minimal implementation can be found in the README.
Improvements
WeakSetpolyfill is no longer necessary- The common size of the polyfill is slightly reduced due to some optimizations.