You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 10, 2022. It is now read-only.
In the above link, the text mentions progressive enhancement but this feels a little misleading. While it is true that a CE can progressively enhance an experience in the context of the page, when talking about an individual CE there is nothing 'progressive' about the enhancement. Progressive Enhancement is a clearly understood term in the web dev world and most people understand it to mean that basic functionality is available to all, with or with JS, and the UX is 'enhanced' or upgraded from that base. It isn't clear in this example that the thing that make its 'enhanceable' is the default slotted content.
Solution
Either remove all mention of progressive enhancement, clarify the use of slots for default/ unitialised content or point users to Web Component/ Custom Element SSR resources so they can learn how to solve this problem.
Appropriate type-something label has been added.
Appropriate section-something label has been added.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Page Affected: https://developers.google.com/web/fundamentals/web-components/customelements#upgrades
What needs to be done?
In the above link, the text mentions progressive enhancement but this feels a little misleading. While it is true that a CE can progressively enhance an experience in the context of the page, when talking about an individual CE there is nothing 'progressive' about the enhancement. Progressive Enhancement is a clearly understood term in the web dev world and most people understand it to mean that basic functionality is available to all, with or with JS, and the UX is 'enhanced' or upgraded from that base. It isn't clear in this example that the thing that make its 'enhanceable' is the default slotted content.
Solution
Either remove all mention of progressive enhancement, clarify the use of slots for default/ unitialised content or point users to Web Component/ Custom Element SSR resources so they can learn how to solve this problem.
type-something
label has been added.section-something
label has been added.The text was updated successfully, but these errors were encountered: