3 ms·
Disabling a broken feature, or not fixing it? The latter is easily explained: Webkit (especially on Linux) is woefully short of manpower now that Google et. al
by creshal 11y ago
Disabling a broken feature, or not fixing it?
The latter is easily explained: Webkit (especially on Linux) is woefully short of manpower now that Google et. al. have pulled out of it.
I'll call myself lucky if WebkitGTK doesn't crash on any of the Alexa top 100 any more.
- josteink 11y agoJust in time for Emacs, XWidget support and Webkit embedded in Emacs then. And here I thought we'd finally get a quality browser-engine for our OS. Seems we'll have to wait some more :)
- creshal 11y agoChromium Embedded Framework (used by e.g. Qt, Android, and browsers like Vivaldi) is okay, and Servo (Mozilla's new rendering engine in Rust) is aiming to be API compatible to it. Seems it's where we're headed for now.