As I understand it's for all the reasons we wanted to have a standalone Necko. For apps that already include GeckoView it kind of comes for free - we just need to expose it.
For app code I would love to use it to avoid all the issues we saw in Fennec whenever we used a different network stack (e.g. downloading favicons). On Fri, Nov 2, 2018 at 2:22 PM Stefan Arentz <[email protected]> wrote: > > > On Thu, Nov 1, 2018 at 5:49 PM Nicholas Alexander <[email protected]> > wrote: > >> > >> - A proposed networking API >> <https://bugzilla.mozilla.org/show_bug.cgi?id=1405081> to expose in >> GeckoView is looking healthy. >> >> > What is the reason for doing network requests through GeckoView? I'm > curious what the use case is. > > S. > > _______________________________________________ > android-components mailing list > [email protected] > https://lists.mozilla.org/listinfo/android-components >
_______________________________________________ Sync-dev mailing list [email protected] https://mail.mozilla.org/listinfo/sync-dev
