-
Notifications
You must be signed in to change notification settings - Fork 101
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 web browsers #266
Comments
That's a good point. We have had informal compatibility targets a year ago, particularly regarding display resolution, based on the demography we observe on our traffic @ landing and blog websites. But it is true that this policy should be a company/product-wide requirement. We will check again how are ours stats regarding that to target X% (e.g. 95%+) and adapt with some heuristics or other stats on top to be a bit broader (e.g.: more users are more likely to be using Windows than our current visitor user base shows). |
Sure. Also we'll need different targets for landing/blog and gitbase-web/bblfsh-web. I think it's safe to assume that the later could support less browsers (it's already the case). |
@smola from https://github.com/src-d/product/issues/302#issuecomment-455313094:
|
Looking at the data segmented by month, it looks like 2 latest for Chrome, 1 latest for Firefox and 1 latest for Safari would cover pretty much our current audience (82%). And 3 latest for Chrome, 2 latest for Firefox and 2 latest for Safari if we want to be more conservative (86%). |
Related to this: src-d/gitbase-web#270
It seems we are targeting very recent Firefox and Chrome versions. It would be good to better define what's our browser compatibility target.
The text was updated successfully, but these errors were encountered: