Chromies,
The Content Modularization and Mojoification effort[1] is well under way with the following major sub-efforts:
- Chrome IPC->Mojo IPC migration.
- UI Service (Mus)
- Network Service
The result of this is a lot of churn in the Content layer & environs as this is one of the most significant architectural changes to the Chrome platform stack since the Content refactor 5+ years ago. As stated previously the goals are hygiene and flexibility through modularization.
As with all large scale changes, there will be bugs. There are problems we don't know about yet, or at least don't know how to solve yet. That's OK. We will work through these in due course, and fix issues as they arise as quickly as possible.
I'm asking for everyone's cooperation in making sure this process goes as smoothly as possible. People working on the initiatives above are already working closely with feature teams to understand the implications of the migration - this collaboration has been fruitful and I hope to see continued constructive dialogue as we rework the innards of Chrome.
Thanks,
-Ben