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
[Schema] Define version number schemas for the different browsers #168
Comments
Lets collect valid versions for UAs. I'm afraid we are not able to code this into the schema, but we need to put it somewhere as a reference for contributors and make it part of a review checklist. Firefox and Firefox for AndroidI think we want to use Firefox versions, not Gecko versions. I'm not 100% sure if we want "55.0" or "55". Leaning towards "55" until I hear differently. ValidFirefox Desktop: "1" - "60" (and higher), "1.5", "3.5", "3.6" Invalid"1.7" (Fx 1) Android WebView, Chrome, Chrome for AndroidChromes wants to display just integers, no "57.0" just "57". Valid"1" - "60" (and higher) Invalid"5.0", "57.0" IE and IE mobileLeaning towards integers for IE as well. ValidDesktop: "1", "1.5", "2", "3", "4", "5", "5.5", "6", "7", "8", "9", "10", "11" Invalid"12", "13" Edge and Edge mobile"The 2-digit EdgeHTML version (12 through 15 so far) is generally how we track web platform support". Valid"12", "13", "14", "15" Invalid"13.11099", "15.14986", "28", "37", "20" SafariI think it makes sense to use "10.0" instead of "10", as there is also "10.1" etc. Valid"1.0", "1.1", "1.2", "1.3", "2.0", "3.0", "3.1", "3.2", "4.0", "4.1", "5.0", "5.1", "6.0", "7.0", "8.0", "9.0", "9.1", "10.0", "10.1". Invalid"536.25" (webkit versions), "6.1.4", "5.2" Safari iOsValidInvalidOperaValid"5.00", "6.00", "7.00", "7.50", "8.00", "8.50", "9.00", "9.50", "10.00", "10.50", "10.60", "11.00", "11.10", "11.50", "11.60", "12.00", "12.10" Invalid"2.4", "2.12" (Presto versions) ServoI think it makes sense to only allow "false", "true", "null" for now as there are no versions, and maybe there won't be any. Valid"false", "true", "null" InvalidAny numbers |
You have the numbering correct for Chrome and Chrome for Android. That scheme also applies to Android Webview. |
I agree that Firefox should be "45" and not "45.0". We only add the decimal point once there's a non-zero digit somewhere after it. |
I also agree that the time has come to bail on Gecko version numbers. Nobody cares anymore about pre-4.0 Firefoxes. :) |
Also Edge is the two-digit EdgeHTML version, according to mdn/kumascript#131 (comment). So "12", "13", "14", "15". I agree that we should use "45" not "45.0" for Firefox, but might we sometimes want to include point releases in the compat data? They do exist after all. |
Thanks for all the comments! I've updated the overview above. |
Safari iOS is tied to the operating system. The operating system definitely has point releases. Not sure where to find a full list. |
Yes, when it’s a point release, we need to say so. So it would go “45”, then “45.0.1”, then “45.1”, then “46”, etc. Use the minimum number of decimal places possible, preferring zero decimal points when possible.
Eric Shepherd
Senior Technical Writer
Mozilla Developer Network <https://developer.mozilla.org/>
Blog: https://www.bitstampede.com/
Twitter: https://twitter.com/sheppy
… On May 10, 2017, at 12:09 PM, wbamberg ***@***.***> wrote:
I agree that we should use "45" not "45.0" for Firefox, but might we sometimes want to include point releases in the compat data? They do exist after all.
|
Wikipedia has a list of iOS releases. The format kind of stinks, but it's pretty thorough: https://en.wikipedia.org/wiki/IOS_version_history |
We need to investigate validating version numbers for different browsers. Otherwise we might end up with inconsistencies like "53.0" and "53", or things like "5.3" which would make no sense for Firefox, for example.
The text was updated successfully, but these errors were encountered: