From MozillaWiki
Jump to: navigation, search

This wiki page is obsolete. The current wiki page about GeckoView is Mobile/GeckoView.


Full Query
ID Priority Summary Status Assigned to
889100 -- Kill the Tabs singleton and move it into GeckoView NEW
891634 -- [meta] Use the appropriate context for global state versus UI operations NEW
927831 P1 [geckoview] Support running without special permissions REOPENED
1033611 -- [geckoview] IndexedDb fails on pages loaded from the Assets using jar:file protocol REOPENED
1033622 -- [geckoview] localStorage fails to load on pages loaded from the Assets using jar:file protocol REOPENED
1037504 P3 [geckoview] Let embedders specify the GeckoView profile name REOPENED

6 Total; 6 Open (100%); 0 Resolved (0%); 0 Verified (0%);


  • [P1] Create a View and support interfaces needed to allow developers to use Gecko in place of a WebView
  • [P1] Create a library (JAR) that makes it easy to pull in the Gecko code into a normal Android application. Devs should not need to build Mozilla/Gecko to get this to work.
  • [P1] Use GeckoView in Firefox for Android as a first class citizen.
  • [P2] We'd like to support using more than one GeckoView in an application.


  • We will not create a system style component that only requires Firefox to be installed. Applications will need to bundle the library into their APK.
  • We will not create a drop-in replacement for WebView. While we'll have the same concepts, we do not intend to chase 1-1 parity with the WebView interfaces.


  • GeckoView is an Android View wrapper around browser.js/browser.xul
    • GeckoView will have an API to allow basic control, such as loading HTML content.
  • GeckoView does not include any browser chrome UI, such as URL editors, toolbar or tab strips
    • Host applications supply the chrome UI
    • Host applications control GeckoView behavior by implementing callback interfaces and providing GeckoView with references to the implementations
    • If the Host provides no implementation, GeckoView is essentially a simple HTML content renderer


ActiveX Wrapper

We used to support an ActiveX wrapper around Gecko. The wrapper had the same core interfaces as the standard MSHTML control that wrapped Trident. You could use Visual Basic, Delphi and even early .NET IDE's to drop the control on your Form. Viola! Gecko HTML renderer in your app. We dropped support because we were constantly chasing the hundreds of interfaces Microsoft supported around MSHTML. Getting the simple stuff to work was one thing. Supporting the rest was unrealistic. Plus, Microsoft kept adding new interfaces. Not all of the concepts matched 1-to-1 with Mozilla concepts, which made truly supporting the interfaces difficult and confusing to use.

System XULRunner

XULRunner is the Gecko-based runtime on desktops. It allows you to build applications like Firefox (XUL-based) using Gecko. This is not an embedding. One of the unrealized dreams of XULRunner was a "Shared Runtime" that could be used by multiple XUL-based apps. Versioning became the nightmare. Updating the shared runtime might break some of the apps using it.


The Mozilla platform has an inherent dependency on profiles, which are used to store various preferences, data files and caches. In the case of an embeddable widget, it's often not desirable to use profiles. Gecko stores the profiles in a location of it's choosing, although this location can be changed as long as Gecko has read/write privileges to the new location. Only one profile can be used by a given process.