Re: [whatwg/dom] Declarative Shadow DOM (#510)

@justinfagnani no, it doesn't:

> I want it to produce HTML files that are indexable by search engines first and foremost.

If it is not part of the native parsing, and everyone is doing whatever mechanism they choose to attach those shadow roots manually, how search engines can reliable determine that those templates should be analyzed and slotted? On the other hand, if is it native, spiders parsers can match the behavior of the browsers including the slotting algo.

> I want my HTML to show consumable content immediately (scripts/modules are deferred because that's how we roll these days).

when is your snipped executed? at the beginning? at the end? per instance (sibling of the `<template>`)? it might be a good enough compromises for some, but not for all. There is a flickering effect if it is at the end, specially if you have styles that can affect the host, etc. So, it is not really solving this.

> I want my HTML to be resilience even when rolling with slow or flaky networks.

Falls short for no JS, or slow networks, or any other similar scenario. In does case, the content will not be consumable.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/dom/issues/510#issuecomment-371241543