-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Consider dropping IE 11 support #6147
Comments
This gets a big thumbs up from me as well, Microsoft is all in on the new version of Edge running Blink and IE11 will only get fixes for very serious issues, it's about as dead in the water as it gets. Furthermore, I would be very surprised if the kind of people who use Gitea are also the same kind of people who use IE11. |
@sondr3 sadly I am one of those people who are required to use IE11 some of the time. Also there are no analytics being collected on the main site. Edit: I do recognize I am in the minority and so I won’t be a blocker to dropping support |
Windows 7 will EOL in around 11 months and from that point on, the only "supported" remaining version will be on Windows 10 LTSB. A shame really that MS does not seem to intend to kill it off entirely. |
Seems to me like breaking compatibility to make a statement should be avoided. However, if maintaining said compatibility actively hinders the development of gitea, then it it should be considered. |
Also notable: GitHub also no longer supports IE11. |
Syntax highlighting is now done in a separate thread which should help performance on large files. The web worker is initialized from a function which is not something IE11 supports and which would force us to create a separate .js file for the worker code. For the reason above, I think it's a good opportunity to end IE11 support with this commit, so it should be landed in the next minor release version. The code uses various ES2017 features and should work in all evergreen browsers. Fixes: go-gitea#6147
I think it's time we do this in the next major version (1.13). |
I think we can put it to milestone 1.13.0 ? |
Indeed, 1.13 was my plan too. |
With master now on 1.13, it's time to drop IE11 for good. The woff variants are also in use by Opera Mini but it has even less market share and I can only imagine how broken the UI is in it. Fixes: go-gitea#6147
* Remove IE11 support With master now on 1.13, it's time to drop IE11 for good. The woff variants are also in use by Opera Mini but it has even less market share and I can only imagine how broken the UI is in it. Fixes: #6147 * update docs Co-authored-by: techknowlogick <techknowlogick@gitea.io>
* Remove IE11 support With master now on 1.13, it's time to drop IE11 for good. The woff variants are also in use by Opera Mini but it has even less market share and I can only imagine how broken the UI is in it. Fixes: go-gitea#6147 * update docs Co-authored-by: techknowlogick <techknowlogick@gitea.io>
This came up in #6139.
In my opinion it's time we drop IE11 support. It's cumbersome to test on for non-Windows users and has a ton of weird bugs that are never going to be fixed. I think we should put a statement to only support modern (evergreen) browsers.
Do we have any statistics how many users use IE on the gitea website?
The text was updated successfully, but these errors were encountered: