Your post brings up a few of the reasons why maintaining an embedding solution is not high on Mozilla's priority list. Embedders each have a different set of problems they are trying to solve and making a modular library stack might be the best way to serve those needs.
However, making a modular library stack is exactly what Mozilla does not want to do, since this is exactly not the problem we are trying to solve. Mozilla wants to make products using the simplest, best methods. Methods that result in the best codesize and performance. One approach Benjamin and others have talked about is trying to find an embedding solution that very closely follows the approach Mozilla takes to building products. Firefox Mobile uses an out-of-process system for rendering web content. The main UI process spawns a separate child process and communicates with that process. User input (mouse and keyboard) are sent to the child process and the web content is rendered to shared image buffers which is then displayed in the parent. The child process doesn't even need a profile folder, one of the big gripes with the current embedding solutions. Would it be possible to create a generic, embedded system to allow a 3rd party application to spawn the child process and display the out- of-process web content? Probably. There are a lot of unknowns and we are still working the kinks out of the system. The biggest advantage to this kind of solution is that it's aligned with how Mozilla is shipping it's own products. Desktop Firefox is moving to the same out-of-process system. There would be a large overlap between Mozilla code and the embedding code. On Apr 6, 8:02 am, "[email protected]" <[email protected]> wrote: > Some thoughts on this ... _______________________________________________ dev-embedding mailing list [email protected] https://lists.mozilla.org/listinfo/dev-embedding
