-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Change Android WebView from 1 to ≤37 for API N-T #10653
Conversation
api/SVGTRefElement.json
Outdated
@@ -44,7 +44,7 @@ | |||
"version_removed": "2.0" | |||
}, | |||
"webview_android": { | |||
"version_added": "1", | |||
"version_added": "≤37", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Due to mdn/yari#3238 this is going to end up looking broken on MDN. This was in Safari 1, so I'm guessing it was enabled with the rest of SVG in some early version of Android WebView? Can you identify that version to avoid this looking broken?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unfortunately I don't have access to many old Android versions at the moment, only 1.0, 1.5, and 4.4, so I can't determine a specific version yet...
api/SVGAnimateColorElement.json
Outdated
@@ -44,7 +44,7 @@ | |||
"version_removed": "2.0" | |||
}, | |||
"webview_android": { | |||
"version_added": "1", | |||
"version_added": "≤37", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This and other cases with "version_removed": "37"
will end up looking broken on MDN due to mdn/yari#3238. It's not so broken that I think it has to change, but if you can find the right version for this now, that would be better.
For the SVG stuff, can you run |
Support for requiredExtensions and systemLanguage in WebKit goes back to when SVG was first shipped: https://trac.webkit.org/browser/webkit/tags/old/Safari-522.11.1b/WebCore/ksvg2/svg/SVGTests.idl https://trac.webkit.org/browser/webkit/branches/old/Safari-3-branch/WebCore/ksvg2/svg/SVGTests.idl Support for SVGTests was added in Firefox 12: https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Releases/12#svg WebView ≤37 is used to match mdn#10653. mdn-bcd-collector has tests: http://mdn-bcd-collector.appspot.com/tests/api/SVGAnimationElement/requiredExtensions http://mdn-bcd-collector.appspot.com/tests/api/SVGAnimationElement/systemLanguage http://mdn-bcd-collector.appspot.com/tests/api/SVGGraphicsElement/requiredExtensions http://mdn-bcd-collector.appspot.com/tests/api/SVGGraphicsElement/systemLanguage These weren't used to confirm the data since it goes so far back, but mdn-bcd-collector at least doesn't constradict any of the added data.
Support for requiredExtensions and systemLanguage in WebKit goes back to when SVG was first shipped: https://trac.webkit.org/browser/webkit/tags/old/Safari-522.11.1b/WebCore/ksvg2/svg/SVGTests.idl https://trac.webkit.org/browser/webkit/branches/old/Safari-3-branch/WebCore/ksvg2/svg/SVGTests.idl Support for SVGTests was added in Firefox 12: https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Releases/12#svg WebView ≤37 is used to match #10653. mdn-bcd-collector has tests: http://mdn-bcd-collector.appspot.com/tests/api/SVGAnimationElement/requiredExtensions http://mdn-bcd-collector.appspot.com/tests/api/SVGAnimationElement/systemLanguage http://mdn-bcd-collector.appspot.com/tests/api/SVGGraphicsElement/requiredExtensions http://mdn-bcd-collector.appspot.com/tests/api/SVGGraphicsElement/systemLanguage These weren't used to confirm the data since it goes so far back, but mdn-bcd-collector at least doesn't constradict any of the added data.
I've sent #10710 and running that against this PR would yield these errors:
I would suggest leaving those as "1" with an issue pointing out which entries are still known to be wrong, along with instructions ( |
But also, some of these entries can probably be removed to sidestep the whole problem. |
I've sent #10714 for one piece that can be dropped. |
Remaining lint errors if applying #10710:
Since these have all been removed, I'd suggest leaving added as "1" and filing an issue about getting the right initial version for SVG in WebView, which involves updating both these remaining 1s and a lot of the new ≤37s. |
I've opened #10790 to discuss this, and will revert the linter-conflicting changes for the time being, until I can find a way to test those other WebView versions! |
A general rule of thumb that I heard and have been going by when updating BCD for WebView Android is that anything added in Chrome 1 will be present in WebView Android 1. However, looking at the difference in WebKit versions (528 for Chrome 1 vs. 523.12 for WebView Android 1), it's simply not plausible that this statement is true -- and after getting my hands on an Android 1.0 emulator, I've confirmed my suspicions. A more accurate rule of thumb would be that "anything present in Safari 3 will be in WebView Android 1".
This PR changes various entries set to WebView Android 1.0 to our range of
≤37
instead after running the mdn-bcd-collector in Android 1.0 and comparing the results to our data. I plan to follow up and replace these ranged values with proper version numbers in the future.