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

Supported browser versions for Admin UI #4676

Open
stennie opened this issue Jun 24, 2018 · 3 comments
Open

Supported browser versions for Admin UI #4676

stennie opened this issue Jun 24, 2018 · 3 comments

Comments

@stennie
Copy link
Contributor

stennie commented Jun 24, 2018

Supported browser versions should be documented so users & contributors are clear on what the admin UI is expected to support.

Older browser versions may continue to work, but won't be explicitly tested or coded for.

Suggested minimum versions to consider:

  • Chrome 57 (released March 2017)
  • Firefox 52 ESR (released March 2017)
  • Internet Explorer 11 (released June 2015 with Windows 10)
  • Edge 38.14393 (released August, 2016)

Chrome has a more aggressive release schedule without Extended Support Releases (ESRs), so the latest Stable version is updated every 6-8 weeks (currently v67 released in May 2018).

@stennie stennie added this to the 4.0 Documentation milestone Jun 29, 2018
@cantuket
Copy link

@stennie thank for clarifying this, but I did find a pretty big bug in IE...

keystonejs/keystone#4769

@stennie
Copy link
Contributor Author

stennie commented Aug 14, 2018

@cantuket I created this as a placeholder proposal for what browser versions should be supported, but this isn't a definitive list yet. The continuous integration tests only run on Chrome & Firefox at the moment, so other browsers like IE, Edge, and Safari rely on manual bug reports and testing.

I suspect your IE11 issue is related to #3734 but need to find some volunteers to investigate the fix.

Regards,
Stennie

@cantuket
Copy link

@stennie thanks, that makes sense.

I actually decided to bump this one instead keystonejs/keystone#4641 because its more recent. The initial solutions proposed wouldn't have been reliable under quite a few scenarios, but I've added some tweaks that will hopefully get us closer.

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

No branches or pull requests

3 participants