-
Notifications
You must be signed in to change notification settings - Fork 130
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Shadow DOM support note #10
Comments
And thank you for such insightful feedback! I'm actually aware of the most recent developments in the space (proof 😇 ), and I tried to bring this up in the article as well:
But even with this fresh addition to Safari you've still only got support in 2 of the big 4 browsers. Not everyone runs the latest versions, so you can safely assume 1 of the big 4. And even for the browsers that do support it, the implementation is far from uniform. If I sound overly negative about the developments in the Web Components space, it's because I was very excited about it when first announced years ago, and then decreasingly confident of their future as time went on. The recent popularity of React doesn't help, as it's publicly stated its opposition to the spec. Still hopeful to be proven wrong, though! :) |
I do not completely agree on counting Safari and Chrome as 1 instead of 2 of the big 4 since they have the user base made almost entirely of the latest version (thanks to Chrome silent updates and update ratio in the first month for iOS & macOS), but my point is not about arguing of this :) but is to give more awareness of the Shadow DOM situation to the readers of your guide. I think we can close the thread here, thanks! |
Thanks for the feedback, I'll definitely adjust my wording towards the positive when I revisit this article! :) |
Whoops, reopening... |
hi,
mentioning your post:
the support/traction of Shadow DOM (especially V1) you are reffering to it's very much an opinion rather than a fact :)
http://caniuse.com/#feat=shadowdomv1
https://blogs.windows.com/msedgedev/2016/02/03/2016-platform-priorities/#pjjDg6AZfqjC9Zc0.97
Chrome supports it (mobile too), latest Safari supports it (mobile too), Firefox and Edge are developing this feature... so it doesn't seem so out of sight.
It would be fair enough if you add this links to give correct informations to readers or specify that is just your personal opinion.
thanks for the great article!
The text was updated successfully, but these errors were encountered: