+++ This bug was initially created as a clone of Bug #191408 +++ See my comment on the cloned bug for reference, if you read carefully I was saying that having WebKit installed on your machine causes Liferea's configure to automatically pick up it as default rendering engine, so we should *disable* it in the parameters we pass to configure script.
Ah, I misunderstood. Of course, just because it's built in doesn't mean you have to use it, unless you've managed to disable all the other backends, which shouldn't be possible in the ebuild. You pick your backend at runtime. That said, maybe I should leave the option for people to play with webkit if they have it installed? I'm undecided... Is there some problem caused by merely having the webkit backend enabled in the build? (I've never tried it personally, because I've never gotten just plain webkit to work well enough to attempt embedding it.)
The problem is that WebKit is picked as default rendering engine if you just have it installed, and there isn't a clear way to pick up rendering engine at runtime. How can i change it back to mozilla? If you want to leave ot let people play with it, I'm with you, as I'd be one of those, but I think then we should override the default to Mozilla.
I'm not sure how to change the ordering... I can't find how to change the rendering engine; that's very very odd. In 1.2, it was just in preferences. I'll bring it up with Lars. I've disabled the webkit backend, but without a bump (since most people won't have webkit, and it's not in portage anyway). Sync in a couple of hours, and you'll get it fine.
