Re: [w3c/webcomponents] Support renaming, aliasing, or namespacing imported elements (#344)

@annevk Thanks for the update. I didn't realise HTML Imports were completely blown off - I guess that means we're stuck, since we're using Polymer which is still based on HTML imports and probably won't implement any aliasing/namespacing on that if it's dead.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/344#issuecomment-279411068

Received on Monday, 13 February 2017 14:44:21 UTC