Workaround HTML Imports bug

#59

Attach import synchronously

• Remove async workaround for Chromium bug #55

Fool Polymer 2.6+ into sending notifications

See #56

Cleanup

• drop support for content attribute #51
• removed bunch of workaround for polyfill bugs #48

Bug fix

• Fix corrupted order of scoped and scopeless nodes in browsers using HTML Imports polyfill #44

2.0.2

Compatibility fix for WCv0 and Polymer 1 to propagate notifications properly to <template is="dom-bind"> that is wrapped in Polymer 2 <dom-bind>. This allows using Polymer 1 in a way that is future compatible with Polymer 2 (#40)

Cross-browser fix

#39

Autonomous Custom Element v1

🎉 The element is now using Custom Elements V1 API!

⚠️ Unfortunately, due to lack of polyfill and browser support, we were forced to drop customized built-in approach. So it's no longer inert <template is="imported-template"> but <imported-template>

⚠️ Currently, it only works in native environments, as there is a bug in webcomponents.js#v1 Html Imports polyfill webcomponents/webcomponentsjs#872. If the bug will not get fixed soon, we will implement a workaround by ourselves.

2.0.1

• Fix pending flag resetting #33
• Dispatch stamped event as Juicy/juicy-html does #32

juicy-html 2.0.0: Content tag split, property setters

Adapted to Juicy/[email protected] - We split content attribute with heuristic detection of URLs vs. inline HTML, to more explicit separate attributes:

• href for URL,
• html for inline HTML content
• Thanks to above, we could now have property setters (reflected into the attributes) for those properties - Plays well with many data-binding systems.