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

Add Web Components 101 series #63

Merged
merged 1 commit into from
May 23, 2021

Conversation

StefanNieuwenhuis
Copy link
Contributor

fix #62

@web-padawan web-padawan merged commit 4b5737b into web-padawan:master May 23, 2021
@web-padawan
Copy link
Owner

web-padawan commented May 23, 2021

@StefanNieuwenhuis I merged the PR, but please correct this statement in the article:

Unfortunately, Safari is falling behind as well and doesn't support Web Components, nor does Apple plan to fully support it in the future. Polyfills must be used for this browser as well.

This is not true: Safari supports web components, except one feature (customized built-in elements) and they have valid objections for it. So I wouldn't say that they are "falling behind". In fact, this statement is confusing and should be rephrased.

@StefanNieuwenhuis
Copy link
Contributor Author

@StefanNieuwenhuis I merged the PR, but please correct this statement in the article:

Unfortunately, Safari is falling behind as well and doesn't support Web Components, nor does Apple plan to fully support it in the future. Polyfills must be used for this browser as well.

This is not true: Safari supports web components, except one feature (customized built-in elements) and they have valid objections for it. So I wouldn't say that they are "falling behind". In fact, this statement is confusing and should be rephrased.

Thanks for merging and I’ve updated the statement about Safari.

@web-padawan
Copy link
Owner

Thanks! I also have to say that "React is catching up fast" is also confusing: they are not. See this issue for some background.

@StefanNieuwenhuis
Copy link
Contributor Author

Thanks! I also have to say that "React is catching up fast" is also confusing: they are not. See this issue for some background.

Thanks again. I've read the thread and did some research and, unfortunately, I came to the same conclusion that React isn't going to support Web Components completely anytime soon...I've updated the article to be more elaborate on this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Web Components 101 series
2 participants