Fix QtWebEngine or work on WebKit?

Continuation of:

Goal:

  • WebKit2 usability
  • load and view dynamic web pages using WebKit2 backend
  • Migrate away from WebKitLegacy branch (i.e. WebKit1)
    • Identify and fix any Webkit2 build issues as needed

Beneifits:

  • runs separate UI split processes for each web browser tab (comparable to QtWebEngine).
    • loading a dynamic web page in a tab doesn’t crash the whole browser
  • better sandboxing
  • No Qt libs dependency
  • Modernization and compatibility to other WebKit2 ports
8 Likes