Scope reduced to just implementing https://github.com/elmsln/unbundled-webcomponents for production usage. This uses the lazy loading methodology of that repo in order to have Drupal super charged with Web components in a lazy loaded way.
Documentation and integration normalized with the rest of the webcomponents modules we support.
Major features of this release:
- 0 config install, now defaults to PSU CDN hosting of assets, critical for trying out webcomponents
- Updated directions settings to match API
- over 98% browser compatibility in browsing traffic
- across theme implementation, build components separate of design to improve portability
Documentation and integration normalized with the rest of the webcomponents modules we support.
Major features of this release:
- 0 config install, now defaults to PSU CDN hosting of assets, critical for trying out webcomponents
- Updated directions settings to match API
- over 98% browser compatibility in browsing traffic
- across theme implementation, build components separate of design to improve portability
We now have a polyfill integration and application development routine in Drupal 7 that's utilizing V1 spec elements in production. The integration method utilized here is the same in the forthcoming HAX module for Drupal 8, and its been demonstrated to work in other platforms as well (HAXcms).
Thus, I am marking this a full release as we are now fully supporting the Web component specification and having a simple way of integrating locally.
Conversion to ES module based integrations. Added support for CDNs and removed core support for HTML Imports / Entity definition building off of polymer files. Enttiy definitions can still be built but not using previous methods. All the code is there to do it but nothing implements the hooks to wire it up. This is an intentional omission and may be added back in at a later date if asked for but this was never reported as used.
Reduced scope of D6 version just to getting things bootstrapped and included in the page load. This is effectively feature complete in that it's able to load web components into D6 and do so over a CDN optionally.
Illogically, I've gone back in time and wrote the Drupal 6 version of this module. Not all of this works, not all of it ever will but it supports autoloading of webcomponents it finds. It also supports autoloading polymer and one page apps.
This now means elements can be developed and deployed against Drupal 6, Drupal 7 and Backdrop. Now for Drupal 8 and beyond..
Breaking change in webcomponents_app which improves the manifest.json structure. Here's an example and it's documented in the webcomponents_app.api.php file:
Fixed some minor notices on edge cases. Big improvement is the addition of the webcomponents_app sub module which can do automatic routing for one-page apps! README.md for details!
support for innerHTML property as well as some additional clean up related to things that would be needed to support solutions like HAX. also fixed some minor bugs
Dependency of libraries API module needed for this to work but wasn't required in the info file causing it to brick on install against minimum requirement sites.
This is the 1st stable release of the webcomponents modules. Most importantly, this has a well documented workflow in README.md on how to use this for production builds of Polymer components via the polymer cli / vulcanize toolsets.