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.

Sign up for GitHub

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

Jump to bottom

Document the supported browsers and general strategy #79

Open
romainmenke opened this issue Oct 19, 2024 · 4 comments
Open

Document the supported browsers and general strategy #79

romainmenke opened this issue Oct 19, 2024 · 4 comments

Comments

@romainmenke
Copy link
Member

romainmenke commented Oct 19, 2024 •
edited
Loading

proposal:

  • support 10 years of browser versions
  • track Blink, WebKit, Gecko, Trident, EdgeHTML
  • do one semver major each year
    • drop all polyfills that are't needed anymore
    • update tested browsers
    • ideally in the fall after Apple ships its latest OS's

Today the supported browser versions would be:

  • IE 11 (because Edge 12 shipped in 2015)
  • Chrome 38
  • Firefox 33
  • Safari 8

This implies:

  • no more android specifics
  • dropping IE 9 and 10
  • dropping Opera Presto (if we still supported that)

Next year we could drop IE completely.
@romainmenke romainmenke mentioned this issue Oct 19, 2024
Merged
romainmenke added a commit that referenced this issue Oct 20, 2024
@romainmenke
set browser targets for babel (#78)
9f25745 
I am unsure what the implicit browser targets are in
`@babel/preset-env`, seems pretty ancient.

I think it is better if we set specific targets and change these over
time as we drop support for some browser versions. (see:
#79)
@romainmenke

This comment has been minimized.

Sign in to view
@mhassan1

This comment has been minimized.

Sign in to view
@mhassan1

This comment has been minimized.

Sign in to view
@romainmenke
Copy link
Member Author

CI tests seem much more solid now, thank you @mhassan1 for working on this!
I am going to close a couple of these comments as resolved to bring this issue back to it's intended topic.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mhassan1 @romainmenke