Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality. Learn more →
Top 23 Webkit Open-Source Projects
-
Playwright
Playwright is a framework for Web Testing and Automation. It allows testing Chromium, Firefox and WebKit with a single API.
-
webview
Tiny cross-platform webview library for C/C++. Uses WebKit (GTK/Cocoa) and Edge WebView2 (Windows).
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
-
browserless
Deploy headless browsers in Docker. Run on our cloud or bring your own. Free for non-commercial uses.
-
WebKit
Home of the WebKit project, the browser engine used by Safari, Mail, App Store and many other applications on macOS, iOS and Linux.
-
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
electrino
Desktop runtime for apps built on web technologies, using the system's own web browser engine
-
SeleniumBase
📊 Python's all-in-one framework for web crawling, scraping, testing, and reporting. Supports pytest. UC Mode provides stealth. Includes many tools.
-
-
-
playwright-go
Playwright for Go a browser automation library to control Chromium, Firefox and WebKit with a single API.
-
Erik
Erik is an headless browser based on WebKit. An headless browser allow to run functional tests, to access and manipulate webpages using javascript.
-
core
Midori Web Browser - a lightweight, fast and free web browser using WebKit and GTK+ (by midori-browser)
-
WebView4Delphi
WebView4Delphi is an open source project created by Salvador Díaz Fau to embed Chromium-based browsers in applications made with Delphi or Lazarus/FPC for Windows.
-
-
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
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.
Project mention: Why Bloat Is Still Software's Biggest Vulnerability | news.ycombinator.com | 2024-02-09You can create the webview using each platforms native GUI toolkit and setup JS communication yourself OR you can use a lightweight library that does it for [1] (search its README for language "bindings").
[1] https://github.com/webview/webview
Project mention: How and why we ripped our Open Source product apart for a full rebuild | dev.to | 2024-02-28The core product is managed, cloud hosted browsers. We run thousands at a time using AWS and DigitalOcean, for people to use with Puppeteer and Playwright scripts. Our container is also available to self deploy under an open-source license.
Project mention: GPU Compute in the Browser at the Speed of Native: WebGPU Marching Cubes | news.ycombinator.com | 2024-04-23Multiple engineers are working on adding it back: https://github.com/WebKit/WebKit/pulls?q=is%3Apr+is%3Aclosed...
Project mention: Show HN: Dropflow, a CSS layout engine for node or <canvas> | news.ycombinator.com | 2024-03-21To reply mostly with my WPT Core Team hat off, mostly summarising the history of how we've ended up here:
A build script used by significant swaths of the test suite is almost certainly out; it turns out people like being able to edit the tests they're actually running. (We _do_ have some build scripts — but they're mostly just mechanically generating lots of similar tests.
A lot of the goal of WPT (and the HTML Test Suite, which it effectively grew out of) has been to have a test suite that browsers are actually running in CI: historically, most standards test suites haven't been particularly amenable to automation (often a lot of, or exclusively, manual tests, little concern for flakiness, etc.), and with a lot of policy choices that effectively made browser vendors choose to write tests for themselves and not add new tests to the shared test suite: if you make it notably harder to write tests for the shared test suite, most engineers at a given vendor are simply going to not bother.
As such, there's a lot of hesitancy towards anything that regresses the developer experience for browser engineers (and realistically, browser engineers, by virtue of sheer number, are the ones who are writing the most tests for web technologies).
That said, there are probably ways we could make things better: a decent number of tests for things like Grid use check-layout-th.js (e.g., https://github.com/web-platform-tests/wpt/blob/f763dd7d7b7ed...).
One could definitely imagine a world in which these are a test type of their own, and the test logic (in check-layout-th.js) can be rewritten in a custom test harness to do the same comparisons in an implementation without any JS support.
The other challenge for things like Taffy only targeting flexbox and grid is we're unlikely to add any easy way to distinguish tests which are testing interactions with other layout features (`position: absolute` comes to mind!).
My suggestion would probably be to start with an issue at https://github.com/web-platform-tests/rfcs/issues, describing the rough constraints, and potentially with one or two possible solutions.
In case anyone else is unfamiliar:
> pywebview uses native GUI for creating a web component window: WinForms on Windows, Cocoa on macOS, QT or GTK on Linux and Kivy for Android.
https://github.com/r0x0r/pywebview
And for Python browser automation, see the SeleniumBase GitHub page!
Playwright
You can check why Mozilla and Apple have opted to not support this.
https://github.com/mozilla/standards-positions/issues/154
https://github.com/WebKit/standards-positions/issues/28
Neither Mozilla or Webkit are satisfied that the proposal is safe by default, and contains footguns for the user that can be pretty destructive.
Leonhard has a pull request in review for adding a “Move” feature: https://github.com/elementary/mail/pull/881
NOTE:
The open source projects on this list are ordered by number of github stars.
The number of mentions indicates repo mentiontions in the last 12 Months or
since we started tracking (Dec 2020).
Webkit related posts
- GPU Compute in the Browser at the Speed of Native: WebGPU Marching Cubes
- HTML Streaming and DOM Diffing Algorithm
- Towards memory safety with ownership checks for C
- WebGPU now available for testing in Safari Technology Preview
- Bun, JavaScript, and TCO
- Show HN: Rem: Remember Everything (open source)
- Disabling iOS Personalized Ads tells kernel to kill daemon every 3 seconds
-
A note from our sponsor - InfluxDB
www.influxdata.com | 25 Apr 2024
Index
What are some of the best open-source Webkit projects? This list will help you:
| Project | Stars | |
|---|---|---|
| 1 | Playwright | 61,568 |
| 2 | webview | 12,005 |
| 3 | playwright-python | 10,675 |
| 4 | browserless | 7,842 |
| 5 | WebKit | 7,438 |
| 6 | wpt | 4,628 |
| 7 | Ultralight | 4,594 |
| 8 | electrino | 4,362 |
| 9 | macdriver | 4,345 |
| 10 | pywebview | 4,302 |
| 11 | SeleniumBase | 4,215 |
| 12 | qawolf | 3,273 |
| 13 | playwright-dotnet | 2,284 |
| 14 | playwright-go | 1,774 |
| 15 | multi | 1,238 |
| 16 | lightdm-webkit2-theme-glorious | 584 |
| 17 | Erik | 576 |
| 18 | core | 366 |
| 19 | WebView4Delphi | 245 |
| 20 | standards-positions | 231 |
| 21 | cog | 216 |
| 22 | 193 | |
| 23 | ios-safari-remote-debug-kit | 168 |
Sponsored
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com