-
Notifications
You must be signed in to change notification settings - Fork 338
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
For each JavaScript component, document all possible levels of progressive enhancement (by browser support) #3227
Comments
I've additionally added Exit this Page to the trello board we're working from. I've tried to be clear that it's not yet published and that there are certain features still being investigated. |
The Trello board we're using to collate this information is here (not publicly viewable): We're meeting to go through the board next Tuesday. |
Playback and team review is happening tomorrow, so I'll move this to In Review. |
The team has reviewed this, and decided to:
|
What
For each level of progressive enhancement, document:
Assume that ES6 is the baseline. Go through the above and see whether an enhancement is optional (can break) or mandatory. For example, we don't mind about adding a comma separator in Character count for
1000
.Consult the designers after we have some reckons on what's optional or mandatory.
Initial timebox: 3 days.
Goal
Settle on some concepts or principles (for example, never hide content) and define what are our core features or components.
Rabbit holes
Don't think about refactoring or rewriting the component, consider the progressive enhancement.
JavaScript components
The text was updated successfully, but these errors were encountered: