Playwright VS qtwebkit

The consensus I could gather is either use playwright or use a workaround to solve it in the puppeteer layer. The root cause of the bug is a websocket size limitation on the CDP protocol for chromium.

With the advent of tools like Puppeteer and now Playwright, end-to-end testing has become much easier and more reliable. For anyone who's used Selenium in the past, you know what I'm talking about. Puppeteer has opened the way in terms of E2E tooling, but Playwright has taken it to the next level and made it easier to await for certain selectors or conditions to be fulfilled (via locators), thus making tests more reliable and less flaky. Also, it's a game changer that it introduced a test-runner - this made the integration between the headless browser and the actual test code much smoother.

In this tutorial, our main focus will be on Playwright web scraping. So what is Playwright? It’s a handy framework created by Microsoft. It's known for making web interactions more streamlined and works reliably with all the latest browsers like WebKit, Chromium, and Firefox. You can also run tests in headless or headed mode and emulate native mobile environments like Google Chrome for Android and Mobile Safari.

// playwright.config.ts import { defineConfig } from "@playwright/test"; /** * See https://playwright.dev/docs/test-configuration. */ export default defineConfig({ testDir: "./src/pages", reporter: "list", use: { baseURL: "http://localhost:5432/", }, timeout: process.env.CI ? 10000 : 4000, // ... more options });

Issues with Playwright

Fast and reliable end-to-end testing for modern web apps | Playwright

This means you cannot place test files outside of this directory, which was brought up as a question on Github some time ago. Initially, I thought it would be nice to add another folder in the repo called "scripts", but Playwright does not allow multiple testDir values.

4.Playwright: Playwright is a browser automation library by Microsoft. Key Features: Supports Chromium, Firefox, and WebKit. Provides cross-browser testing capabilities. Allows automating web, mobile, and desktop applications

HTML to PDF conversion is a common requirement in modern web applications. It allows users to save web pages, reports, and other content in a format that is easy to share and print. There are many libraries and services available for converting HTML to PDF, each with its own strengths and weaknesses. In this article, we will compare some of the most popular HTML to PDF renderers in Node.js, including Puppeteer, Playwright, node-html-pdf, and Onedoc.

Playwright [ https://playwright.dev/ ] ✅

Not so ancient - Otter uses QtWebKit 5.212 from Mar 10, 2020.

AFAIK, Otter Browser uses the latest QtWebkit-ng on Windows. It scores 341 points in HTML5Test. There is also an experimental Qt WebEngine backend.

The main backend for Otter Browser is QtWebkit Reloaded, last updated in 2020, see the screenshot.

As for Otter Browser, there is a bug in QtWebKit. Try using Otter Browser on Qt WebEngine.

Otter Browser is based on QtWebKit-NG, which is from 2020, so still relevant. That said, you can use the nightly WebKit build from Playwright: https://i.postimg.cc/Fz7FwRQW/Playwright.png

Lastly, the other webkit based project, QtWebkit. It is also very lightweight and fast, It also provides a cross-platform render and It has access to the system dialogs. The down side is that you will have to make a Qt App to use it. If you don't want to implement it, then you cannot use It

> I hate that it's based on Chromium though

There aren't really many alternatives. The main one is WebKitGTK, but that comes with its own set of issues (mostly performance/compatibility). You can use qutebrowser with QtWebKit as well, but I wouldn't recommend it - it's based on a 2018 WebKit with many known security issues: https://github.com/qtwebkit/qtwebkit/releases

I had hoped for Servo to fill that gap at some point, but so far that hasn't happened yet: https://github.com/servo/servo/issues/27579

Another possibility is for Geckoview to be ported to Desktop platforms some day: https://mozilla.github.io/geckoview/ - something the people behind Tridactyl would like to happen: https://tridactyl.xyz/ideas/#port-geckoview-to-x86_64

> and Qutebrowser privacy related settings also seem quite limited compared to Firefox... (and even compared to Chromium.)

Can you be more specific? Pretty much anything that's possible to expose (either via a QtWebEngine API or via Chromium commandline arguments) is exposed. Certain things (like deleting cookies belonging to a tab when it's closed) just aren't possible without implementing them in QtWebEngine first unfortunately.

FWIW there's an overview here: https://github.com/qutebrowser/qutebrowser/issues/4045

and Qt has mostly moved to qtwebengine/blink. qt-webkit is sort-of-not-really maintained by very few volunteers. https://github.com/qtwebkit/qtwebkit/releases

While you can still use it with QtWebKit instead, I wouldn't recommend doing so, as that's still based on a 2018 WebKit with no process isolation or sandboxing.