- From: Takayoshi Kochi <notifications@github.com>
- Date: Wed, 16 Aug 2017 10:07:31 +0000 (UTC)
- To: w3c/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 16 August 2017 10:07:55 UTC
> To be clear, I was asking why the inline HTML case was necessary. I am perfectly happy with importing from a URL. Ah, okay. > It's a good point that import statements need to be statically analyzable. Perhaps "import as" with a Symbol.importer could be used with dynamic import() only? As @rniwa wrote in https://github.com/w3c/webcomponents/issues/645#issuecomment-310823900 , MIME type can be used to infer the object type without `as X`, I think for some known MIME types we can make them work. But I have no idea how custom importer can work for static imports. @rniwa might have an idea. -- 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/645#issuecomment-322725355
Received on Wednesday, 16 August 2017 10:07:55 UTC