All of them! So I assume that the WKWebView that we use already provides a good amount of HTML5 APIs. But we need to be sure. So my questions to this larger audience are:
* Is there some kind of feature test that we can run in a WKWebView to find out the status of API availability? Ideally something that generated a report that we can diff against the results of Firefox (for Android). * What are the absolute minimum APIs that we need to support to be awesome? Note that we can inject user scripts into WKWebView. These are things can be injected at document start or end. So that means that if things are missing that we think are important, we can create a js implementation or even bridge to native code if needed. S. _______________________________________________ mobile-firefox-dev mailing list [email protected] https://mail.mozilla.org/listinfo/mobile-firefox-dev
