Resurrecting Embedded Gecko

Andrew Sutherland asutherland at asutherland.org
Wed Feb 3 08:30:45 UTC 2016


I don't think a more supported embedding mechanism is likely to offer
Thunderbird any implementation solace.  Thunderbird is integrated into
the guts of Gecko in places that a normal embedding API wouldn't cover
and in ways that Connected Devices is unlikely to need[1].

Assuming Thunderbird rids itself of the problematic Gecko-coupling and
migrates to a more HTML/JS/etc. world, it's not clear that sticking with
Gecko as an embedding would be good for anything but nostalgia purposes.
 Efforts like https://github.com/atom/electron seem like they have
serious ecosystems built-up around them in a way that is unlikely to
happen for even a supported Gecko embedding anytime soon.

Andrew

1: For example, nsIContentPolicy that Thunderbird uses for its message
reader display would be a reasonable embedding API exposure.  But
Connected Device efforts are extremely unlikely to ever need that API
themselves because any needs along those lines should instead be met by
use of CSP or service-workers instead.


More information about the tb-planning mailing list