Ability to embed Gecko as an alternative to Chromium Embedding Framework

[alexdelorenzo]

This would allow for Electron-like frameworks that work on top of Gecko and SpiderMonkey instead of Chromium via CEF.

It would also be good for embedding webpages in desktop applications. As it stands, CEF is the go to for this along with some WebKit-based options like WPE.

[saluki]

I really want something like this. Please.

[Ixxa]

If this idea is considered, I think the objective should be to implement it how Webview2 is in terms of functionality instead of CEF because the later is much more heavy on resources usage compared to the former.

[nose_gnome]

I hope this happens.  It's been in review for quite a while now, have there been any changes/updates about this since?

[Focuz]

I don't think there's ever been a better time to start making major pushes for this given all the current hype around the ECMA/JavaScript ecosystem; it would be great if developers had a choice over libcef.

Letting us use Gecko instead of just Chromium would mean that big companies like Google and Apple aren't the only ones deciding how the web works. It's about giving developers choices and keeping the web open for everyone.

[Anonymous]

Hey, guys,

I would like to comment on this if this feature is developed here, perhaps a commercial advantage for Mozilla Firefox. Because most programs I use the structure called "electron" (which chromium - which is the open source alternative to google chrome browser) with html/css/js. Perhaps with these features, developers can use the gecko in the application development environment (Electron) or have an alternative with this - chromium and gecko options.

[Pentore]

is there an update? since chrome is getting more garbage from time to time, and google is ruining it even more. gecko could make an perfect replacement for embedded browser engines. im really looking forward to see some impact.

[NJK0]

This is pure speculation, but I think Mozilla isn't allowed (by the big players maybe?!) to implement this, in order to stop Firefox from being way too popular!
Why else wouldn't Mozilla give this issue a high priority?

[janbrasna]

For anyone not old enough to remember the days when Gecko embedding was a thing:

• https://www-archive.mozilla.org/projects/embedding/
• https://www-archive.mozilla.org/projects/embedding/embedoverview/EmbeddingGecko.pdf

And when it was abandoned:

• https://groups.google.com/g/mozilla.dev.embedding/c/c_NMcO-N8wo
• http://www.h-online.com/open/news/item/Mozilla-kills-embedding-support-for-Gecko-layout-engine-Updat...

The reasons were described back then, question is if such limitations are still limiting today.

[foxpro]

There is servo which is designed to be embeddable, but it's far away from being usable, so hope Gecko will finally become embeddable, I would be happy to develop applications and game UIs based on it.

[Teknevra]

Feature Suggestion: Offer Gecko as an Alternative to Chromium

##### Overview:

Firefox, powered by the Gecko engine, stands out in the browser landscape as one of the few major browsers not based on Chromium.

With the integration of Quantum, Firefox has significantly enhanced performance, privacy, and security, further distinguishing itself from Chromium-based browsers.

Given these unique attributes, I would lilike to propose that Mozilla explore potentially offering Gecko as a viable alternative to Google/Chromium for developers and other browser projects.

________________________________

### Proposal:

**1. Open-Source Collaboration:**
- Expand the open-source community around Gecko, encouraging developers to contribute to its development.
- Provide comprehensive documentation and support for developers interested in integrating Gecko into their projects.

**2. Promote Gecko's Unique Features:**
- Highlight the distinct advantages of using Gecko, such as improved privacy features, enhanced security, and superior performance with Quantum integration.
- Showcase successful case studies or projects that have effectively integrated Gecko.

**3. Develop a Developer Toolkit:**
- Create a toolkit or SDK that simplifies the process of building applications or browsers using Gecko.
- Offer tutorials, sample code, and other resources to assist developers in adopting Gecko.

**4. Engage with Browser Developers:**
- Actively reach out to browser developers who may be interested in exploring alternatives to Chromium.
- Host workshops, webinars, or conferences to discuss the potential of Gecko as a competitive rendering engine.

**5. Establish Partnerships:**
- Collaborate with organizations and educational institutions to promote Gecko as a teaching tool for web development.
- Partner with tech companies that are looking for non-Chromium-based solutions to diversify their product offerings.

_________________________________

### Benefits:

- **Diversity in Browser Engines:** Offering Gecko as an alternative can help increase diversity in browser engines, reducing reliance on Chromium.
- **Innovation:** Encouraging more developers to use and contribute to Gecko can drive innovation and improvements in web technologies.
- **Privacy and Security:** By promoting a browser engine focused on privacy, is open-sourced, and security, Mozilla can further its mission of creating an open and accessible internet for all.

• Potential Steady Cash Flow: Licensing Gecko for commercial use or offering premium support services could provide Mozilla with a steady cash flow, supporting further development and sustainability of the project.

_______________________________________

### Conclusion:

By positioning Gecko as a robust Open-sourced alternative to Chromium, Mozilla has the opportunity to foster greater diversity and innovation within the web ecosystem.

This initiative could attract developers seeking alternatives and strengthen Firefox's role as a leader in promoting an open and secure internet.

[Jon]

(Note: similar ideas have been merged into this thread)