Mark Mayo, Mozilla CEO and chief manager of Firefox, has introduced project Tofino. In that project, there are a number of GUI experiments for a web browser which Mozilla is working on. Firefox development is not going to be affected but it's a fact that Firefox usage has been going down steadily. It is interesting that the whole project is built on top of a Chromium-based engine Electron, created by GitHub for Atom editor. Instead of XUL used in Mozilla, the browser's user interface is created using React.
The Electron platform allows developers to create standalone apps based on technologies used in browsers. It is possible to use Node.js and its modules, extended APIs to create dialogs, context menu, window management, file system access and so on. Electron is considered as a perspective project which will affect the future of the browser technology stack.
While Electron is based on Chromium, Mozilla developers are going to use it for a limited time and have no plans to cancel Firefox's Gecko engine development. Along with Tofino, a new project, named Positron, was started to create the Electron API over the Gecko engine. Positron includes yet another project - Spidernode - which is a Node.js implementation with the SpiderMonkey engine instead of the V8 engine. It is possible to see an API layer for V8 API emulation on top of SpiderMonkey.
After Positron and Spidernode will be finished, the Tofino project can be compiled without Electron. The Electron project was selected as an easy-to-use platform to create a prototype of the new user interface for the browser. The new UI is the primary goal of the project. As for the engine, it will not replace Gecko or the upcoming rendering engine Servo in Firefox.
Tofino will not become a standalone finished browser. With experiments in Tofino, Mozilla developers hope to create a new kind of user interface. They consider the tab based interface as deprecated and ineffective for modern Web-based reality. The new user interface will fit PC and mobile use cases better than tabs, be more productive and task oriented. If it is a big success, maybe one day in the distant future we might see a completely different Firefox browser.
Winaero greatly relies on your support. You can help the site keep bringing you interesting and useful content and software by using these options:
9 thoughts on “Mozilla is experimenting with Chromium based browser”
Thank you for very interesting article.
Once upon a time, there were many different browser (IE, Firefox, Opera…the real one, etc), with different engines, like Trident, Gecko, Presto etc.
Now we’re going to have only one browser (Chrome and Chromium clones) and that is is very disappointing.
So when Firefox will become another Chrorme clone, I will stop using it and continue using Palemoon only.
if this will happen (which Mozilla do not confirm), I will switch to Vivaldi.
Vivaldi has a nice gui, but of course is another Chrome clone, like Opera 15+ and the others.
So far Qupzilla has been a valid alternative, but now (version 2.0) is a multiprocess browser with a Firefox-like gui.
So now my only hopes are Palemoon and Otter browser.
And of course I’m still using Opera 12.x.
I don’t believe in future of the Otter browser. Too small team, too depends on enthusiasm.
As for Qupzilla, last time i tried it, I faced with too often crashes and – which is worse – small extension amount. It was 1.6.x I guess.
Otter could be the new Opera 12.x, but of course its team is so small that it has a very very very slow development.
Palemoon is a fork of Firefox instead and won’t follow its new trend of development: Palemoon won’t become a multiprocess browser and won’t try to imitate Chrome in its gui and stupid setting panel, so why don’t believe in it?
I like options and customizations and hate multiprocess browsers that eat too much RAM, so I think I have no choice: Palemoon and the real old Opera.
I don’t believe in Palemoon for the reason of the small team.
One day they will cancel the project.
Even if they cancel, someone else can fork it right?