> 2) We have no easy way to reference Android assets. That is, we have no > equivalent of WebView's file://android_asset. I think GeckoView consumers > will want this; it's the easiest way (by far!) to ship static assets as part > of your Android application. (We already did lots of work [4] [5] to ship > libraries and omni.ja itself in assets/, with an eye to making IDE builds and > shipping GeckoView-based applications easier.) This is surprisingly easy to > arrange; I've updated Bug 948465 with some thoughts [6].
We do support the drawable: scheme: android/modules/WebappManager.jsm:311: icon: "drawable://alert_app", _______________________________________________ mobile-firefox-dev mailing list [email protected] https://mail.mozilla.org/listinfo/mobile-firefox-dev
