Skip to content
This repository has been archived by the owner on Aug 10, 2022. It is now read-only.

misleading copy about Custom Elements and Progressive Enhancement #9541

Open
2 tasks
pngwn opened this issue Mar 17, 2022 · 0 comments
Open
2 tasks

misleading copy about Custom Elements and Progressive Enhancement #9541

pngwn opened this issue Mar 17, 2022 · 0 comments

Comments

@pngwn
Copy link

pngwn commented Mar 17, 2022

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.

  • Appropriate type-something label has been added.
  • Appropriate section-something label has been added.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant