Skip to content
This repository has been archived by the owner on Aug 22, 2024. It is now read-only.

Settle minimum browser version required #98

Open
Kebap opened this issue Jun 4, 2020 · 10 comments
Open

Settle minimum browser version required #98

Kebap opened this issue Jun 4, 2020 · 10 comments
Labels
documentation Improvements or additions to documentation

Comments

@Kebap
Copy link
Contributor

Kebap commented Jun 4, 2020

Any ideas where we draw lines?

Some folks like to play Mudlet on old Win XP or Linux versions from years ago. These will probably ship outdated browsers as well.

How far back do we need ir want to support them?

This may influence ability to use certain features or no.

@vadi2
Copy link
Member

vadi2 commented Jun 5, 2020

I'd say whatever win7 supports - so ie11. Respective Firefox and Chrome versions too.

@SlySven
Copy link
Member

SlySven commented Jun 5, 2020

How do you set a limit - or is it a question of not using things that older browsers won't handle? Also does it involve testing something in the End-users browser? I hope it doesn't come down to agent-string sniffing as that is just not reliable...

@vadi2
Copy link
Member

vadi2 commented Jun 5, 2020

Right, just a matter of how much of a headache are we willing to do to support older browsers.

@Kebap
Copy link
Contributor Author

Kebap commented Jun 5, 2020

not using things that older browsers won't handle

This.
Which bleeding edge features can we use?
At what point do we stop paying attention to older browsers?
When will we say "no" to a person asking for help playing Mudlet on their grandma's old hardware?
Obviously the Mudlet client as an application can be tweaked, but this repo relies on the browser.

@Kebap Kebap added documentation Improvements or additions to documentation question Further information is requested labels Jun 5, 2020
@vadi2
Copy link
Member

vadi2 commented Jun 6, 2020

There's a great website https://caniuse.com for this, once we settle on the minimum browser version.

@vadi2
Copy link
Member

vadi2 commented Jun 6, 2020

Since the start of the year, these are the browsers used on our websites that have passed the 1% barrier:

image

I think the worst browser we need to worry about is Internet Explorer. Unfortunately the stats can't show us what version of it are people using, but I think whatever version an updated Windows 7 installation has would be good enough.

@Kebap
Copy link
Contributor Author

Kebap commented Jun 8, 2020

I think Matomo can list browser versions as well... need to remember where exactly :)

@Kebap
Copy link
Contributor Author

Kebap commented Oct 20, 2020

whatever win7 supports - so ie11. Respective Firefox and Chrome versions too.

  • Internet Explorer - v11
    • Even though this version is not updated by Mircosoft anymore (they since switched to Edge) Win7 is still running this
  • Firefox - current
  • Chrome - current
    • Google has promised to keep new Chrome versions working on Win 7 until at least 2021-07

@vadi2
Copy link
Member

vadi2 commented Oct 20, 2020

That sounds good to me!

@Kebap Kebap removed the question Further information is requested label Oct 20, 2020
@SlySven
Copy link
Member

SlySven commented Oct 23, 2020

For FireFox you'd probably also want to handle the ESR version.

As an aside GitHub is playing silly buggers in that they have go so bleeding edge that they are not supporting my browser choice any-more - though someone has come up with an XPI (not something that Mozilla touches nowadays) addon https://github.com/JustOff/github-wc-polyfill/ that fixes things (since the person released it a few days ago they have broken things further and an update to the fix has become necessary) - what is scary is that GitHub is the location of the repository for the browser so that they (GH) are helping to prevent the developer not to be able eat their own dog food...

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

3 participants