- From: Joshua Nelson <notifications@github.com>
- Date: Sun, 22 May 2016 17:14:12 -0700
- To: w3c/webcomponents <webcomponents@noreply.github.com>
- Cc:
Received on Monday, 23 May 2016 00:14:43 UTC
In addition to @treshugart 's use case, I can imagine another where components have dynamic content – say, for example, an i18n component: `<x-i18n key="my.string"></x-i18n>` -> `<x-i18n>Value of my string</x-18n>` It seems to me that search engines should have the same power as a user when it comes to parsing web pages – and a user has the ability to see the contents of the shadow DOM. At least for now, I guess people who use components that have SEO and a11y concerns should use shadow dom mode=open. --- 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/500#issuecomment-220865292
Received on Monday, 23 May 2016 00:14:43 UTC