Isn't that the point? Making the engine decoupled and embeddable just wasn't on Mozilla's radar, and it suffered as a consequence. Chrome team was advcied very

Isn't that the point? Making the engine decoupled and embeddable just wasn't on Mozilla's radar, and it suffered as a consequence. Chrome team was advcied very early in their development by none other than Android team to go for WebKit because it was easier to work with. Not Presto, not Gecko. So at least since back then, thud feature was at least somewhat on Apple's list of priorities. I'm not sure if it got carried over from KHTML, but if it did, they didn't break it intentionally. Back in IE horror days I remember using Avant Browser. It used IE to provide fancier features like tabs. I never remember Gecko anywhere in discussion for being a platform to build on top of, except for other Mozilla projects (FFOS, Thunderbird) that Mozilla dropped sooner or later.