Skip to content
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

Open
moebiusmania opened this issue Nov 11, 2016 · 4 comments
Open

Shadow DOM support note #10

moebiusmania opened this issue Nov 11, 2016 · 4 comments

Comments

@moebiusmania
Copy link

hi,
mentioning your post:

If you're familiar with the Web Components spec, think of this as getting the style isolation benefits of the Shadow DOM without having to care about browser support (or whether or not the spec ever gets serious traction).

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!

@jareware
Copy link
Owner

thanks for the great article!

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:

Despite some recent glimmers of hope, the Web Components spec hasn't made great progress in recent years

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! :)

@moebiusmania
Copy link
Author

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!

@jareware
Copy link
Owner

Thanks for the feedback, I'll definitely adjust my wording towards the positive when I revisit this article! :)

@jareware
Copy link
Owner

Whoops, reopening...

@jareware jareware reopened this Nov 14, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants