Re: [w3c/webcomponents] HTML module should require a new top level element (#752)

It's not clear they're faster. E.g., you need to parse until the end before you can do anything, since you might encounter a well-formedness error (unless we do XML5, which still seems like a good idea). And they're not always as optimized as HTML parsers with interning of common element and attribute names, buffers optimized based on average documents on the web, etc.

-- 
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/752#issuecomment-459368703