Gecko Engine
As mentioned in the Technical Overview, all of Quira's layers sit on top of a rendering engine. Quira uses a soft fork of Gecko (Mozilla's rendering engine) rather than Chromium.
Why Gecko, not Chromium?
- Engine independence EChromium holds 80%+ market share. A Gecko-based browser contributes to web engine diversity.
- WebExtensions MV2 + MV3 EUnlike Chrome which has fully deprecated MV2, Gecko continues to support both manifest versions.
- Proven fork path EZen Browser and Floorp have demonstrated that Gecko soft forks can ship production-quality browsers in 3-6 months.
- Servo components already integrated EFirefox already includes Servo-derived Stylo (CSS engine) and WebRender (GPU rendering).
Future Servo migration path
| Phase | Engine | Rationale |
|---|---|---|
| Phase 1 (0-12 months) | Gecko fork | Ship-ready, full WebExtensions support |
| Phase 2 (12-24 months) | Gecko + Servo subview | Experimental Servo for AI-generated content views |
| Phase 3 (24+ months) | Migration decision | Full Servo migration if WPT pass rate exceeds 90% |
Was this page helpful?