> I entirely agree that the current Firefox protocol is also proprietary. > However I also assumed that it's considered an internal implementation > detail rather than something we would expect people to interoperate with. If > that wasn't the case then I apologise: I should have complained earlier :)
We would like a console and debugger for Servo, and those seemed pretty common. We did an initial implementation of the Firefox protocol, but hat protocol changed out from under us, and some of the work we did broke and wasn't not easily fixable. At the very least there is a desire to interoperate between Servo and Firefox and the current protocol isn't very helpful for this. The Chrome one has a huge advantage of being documented, even if not all the semantics are. I was also under the impression that the design of the Chrome protocol is better than the Firefox one because you can ingest the JSON messages and only handle the things you want. It seems like that would make it more robust to future changes. Is there another alternative besides CDP you'd like to propose? I think there's a strong case that doing something besides the current Firefox protocol is a good idea, and the CDP seems to have some nice qualities. Is there an alternative that is also suitable, or is the preference that we simultaneously get involved in standardizing CDP (or at least ensuring that all parties are amenable to doing that work)? jack. _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
