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

Update our browser support strategy #2718

Closed
4 tasks done
querkmachine opened this issue Jul 20, 2022 · 5 comments
Closed
4 tasks done

Update our browser support strategy #2718

querkmachine opened this issue Jul 20, 2022 · 5 comments
Labels
epic Epics are used in planning project boards to group related stories tooling

Comments

@querkmachine
Copy link
Member

querkmachine commented Jul 20, 2022

What

We're looking to move to a graded system for defining the support received by the different browsers out there. This system will define not only in which browsers features run, but also the level of testing we intend to do with them and the priority we'll give to bugs.

Why

Currently Frontend uses specific versions of particular browsers to determine the minimum level of browser support and what polyfills/prefixes are needed: principally Internet Explorer 8 and Safari 9, which indirectly provide support for older versions of 'evergreen' browsers.

As we transition into reducing support for IE11, and dropping all supporting for IE8–10, we want to reassess how we decide how our minimum level of browser support will work in a world where we only (or mainly) support evergreen browsers.

Who needs to work on this

Developers, content designers

Who needs to review this

Developers, content designers

Done when

Tasks

  1. javascript
  2. javascript
    domoscargin
  3. documentation javascript
    claireashworth
@querkmachine querkmachine added the awaiting triage Needs triaging by team label Jul 20, 2022
@querkmachine querkmachine added tooling javascript squad and removed awaiting triage Needs triaging by team labels Jul 20, 2022
@querkmachine
Copy link
Member Author

I started writing a document (internal only) positing various methods that we could determine future browser support.

@36degrees 36degrees self-assigned this Nov 30, 2022
@kellylee-gds kellylee-gds added the epic Epics are used in planning project boards to group related stories label Jan 31, 2023
@stevenjmesser
Copy link

stevenjmesser commented Jan 31, 2023

We've unpacked the work needed to come to a decision on future browser support. It's kept in a Trello board which isn't open, but we'll add discrete actions to the team board.

@romaricpascal romaricpascal changed the title Decide on Frontend's future browser support Update our browser support strategy Mar 31, 2023
@stevenjmesser stevenjmesser modified the milestones: v5.x-candidate, v5.0 May 17, 2023
@36degrees 36degrees removed this from the v5.0 milestone Jun 27, 2023
@36degrees
Copy link
Contributor

Main things left to do:

  • Understand how browser support applies to CSS
  • Review the existing draft and see if we can simplify it at all – see if rationale can be split out into a decision record / the PR
  • Move browser support details from README to frontend docs and update

@romaricpascal
Copy link
Member

README details are within the Browser and assistive technology support section

GOV.UK Frontend supports:

@36degrees
Copy link
Contributor

Gonna call this done!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
epic Epics are used in planning project boards to group related stories tooling
Projects
None yet
Development

No branches or pull requests

5 participants