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

For each JavaScript component, document all possible levels of progressive enhancement (by browser support) #3227

Closed
Tracked by #2718
stevenjmesser opened this issue Jan 31, 2023 · 4 comments

Comments

@stevenjmesser
Copy link

stevenjmesser commented Jan 31, 2023

What

For each level of progressive enhancement, document:

  1. Browser features or APIs required
  2. Browser features or APIs that could be polyfilled
  3. Browser grade necessary for the enhancement
  4. Whether the enhancement is optional (can break) or mandatory

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

  • Accordion
  • Button
  • Character Count
  • Checkboxes
  • Details
  • Error Summary
  • Header
  • Notification banner
  • Radios
  • Skip link
  • Tabs
@owenatgov
Copy link
Contributor

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.

@36degrees
Copy link
Contributor

The Trello board we're using to collate this information is here (not publicly viewable):
https://trello.com/b/REPdiaeT/govuk-frontend-js-component-features

We're meeting to go through the board next Tuesday.

@stevenjmesser
Copy link
Author

Playback and team review is happening tomorrow, so I'll move this to In Review.

@domoscargin
Copy link
Contributor

domoscargin commented Feb 15, 2023

The team has reviewed this, and decided to:

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

No branches or pull requests

7 participants