Open Croydon opened 7 years ago
Servo removed the support for CEF for the moment. https://github.com/servo/servo/issues/9147#issuecomment-411944715
Waiting for it to (hopefully) come back...
Hopefully.
The idea is that servo gets rid of the CEF API to improve the usability of servo in all kinds of applications. Servo is already aimed at being embeddable and in some way they established concepts superior to CEF's "you get chrome and some layer on top to disable features and make it embeddable". Instead you get "these are the bare components, use them to build a browser, or whatever"
Okay, I looked into servo some more regarding the issues:
There are a lot less dependencies for Servo than for CEF, building should be much more straight-forward.
@Croydon: what do you mean by
Blocked by https://bugzilla.mozilla.org/show_bug.cgi?id=1386669 & https://bugzilla.mozilla.org/show_bug.cgi?id=1386674
Servo is used in firefox already, so why are these blocking?
Servo is used in firefox already, so why are these blocking?
There is a huge difference between using parts of Servo in Firefox (this is the case) and having full Servo in Firefox, which will still take same time and maybe a long time.
These meta bugs I linked to can be a good indicator and how stable Servo as a whole is.
As far as we evaluated on the hackathon #608 Servo will remain unfit for our use in the realistic future.
This might solve problems like #490, #371
Blocked by https://bugzilla.mozilla.org/show_bug.cgi?id=1386669 & https://bugzilla.mozilla.org/show_bug.cgi?id=1386674
On the downside:
https://hackmd.io/BwJhEMQMwZgBgLQDYCsBTKCAsBjAjJsFgJxoLErEjAzF4gAmMaQA# https://bugzilla.mozilla.org/show_bug.cgi?id=1311790 https://github.com/servo/servo/tree/master/ports/cef https://github.com/servo/servo/issues/9147