IssueRaiser

Rekonq is dead (as a project I mean), and I've seen plenty of compatibility problems, with rekonq, qupzilla or even the test browser (i.e.

Rekonq is dead (as a project I mean), and I've seen plenty of compatibility problems, with rekonq, qupzilla or even the test browser (i.e. the problem is with the engine). FWIW epiphany (or "web", as is it called now) is GTKwebkit based and crashes just as often. Qupzilla-git i.e. the version based on Qtwebengine is getting there, so reasonably soon we may have a decent Qt-based browser (I don't doubt scrollaway knows that). Also the fiber browser looks promising. I do think we need a way to do CI between chromium and Qtwebengine, or else we'll end up shipping browsers lagging one or two versions behind chromium. As far as gecko goes, I think it's over. The hope is servo, which being much more modular may be integrated without struggling with XUL.

Posted by baghira on Jul 24, 2015, 8:35 AM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.5,000 issues0 comments

hackernews (Logistics)

Rekonq is dead (as a project I mean), and I've seen plenty of compatibility problems, with rekonq, qupzilla or even the test browser (i.e.

baghiraJul 24, 2015, 8:35 AM

Rekonq is dead (as a project I mean), and I've seen plenty of compatibility problems, with rekonq, qupzilla or even the test browser (i.e. the problem is with the engine). FWIW epiphany (or "web", as is it called now) is GTKwebkit based and crashes just as often. Qupzilla-git i.e. the version based on Qtwebengine is getting there, so reasonably soon we may have a decent Qt-based browser (I don't doubt scrollaway knows that). Also the fiber browser looks promising. I do think we need a way to do CI between chromium and Qtwebengine, or else we'll end up shipping browsers lagging one or two versions behind chromium. As far as gecko goes, I think it's over. The hope is servo, which being much more modular may be integrated without struggling with XUL.

Comments (0)

No comments yet. Start the discussion.

Comment on this issue