html2svg VS BrowserBox

I've opened an issue to track PDF support [0], you can subscribe to get progress updates for this specific feature. For general project updates you can use the "Watch" button on the repository to get commit updates on your feed.

[0] https://github.com/fathyb/html2svg/issues/3

The codebase for html2svg is very simple and building is done using 4 commands. It uses Electron.js, which in itself is a fork of Chromium with all the build infrastructure to apply patches dynamically. I'm preparing merge requests to submit all changes in skia.patch to the upstream. If all are accepted, we'll only need ~200 lines patched in Chromium.

Hey HN! Today, we're proud to introduce BrowserBox Pro, a powerful tool for businesses seeking a secure and reliable browser automation solution for RPA, testing, and more. Our goal is to provide an exceptional product that meets your corporate needs while supporting the ongoing development of BrowserBox.

BrowserBox Pro (Polyform): https://github.com/dosyago/BrowserBoxPro

BrowserBox (AGPL): https://github.com/dosyago/BrowserBox

Why choose BrowserBox Pro?

Enhanced Security: BrowserBox Pro is built with advanced security features, providing an isolated browsing environment to protect sensitive data and ensure secure online interactions.

Powerful Automation: Our solution simplifies RBI, RPA and testing processes, offering seamless integration with your existing workflows and saving you time and resources.

Customization & Scalability: BrowserBox Pro is designed to be flexible and adaptable, catering to a variety of use cases and scaling effortlessly as your business grows.

Dedicated Support: We offer comprehensive documentation and timely support, ensuring your team has the resources needed to maximize BrowserBox Pro's potential.

Continued Innovation: By licensing BrowserBox Pro, you contribute to the ongoing development and improvement of both BrowserBox and BrowserBox Pro, ensuring a cutting-edge product that evolves with your needs.

Open Source Commitment: We're thrilled to announce that BrowserBox is now open source under the AGPL license. This enables a strong community around the project, encourages contributions, and ensures transparency in its development. We believe in giving back to the community while offering a robust and secure solution for businesses through BrowserBox Pro.

We invite you to explore BrowserBox Pro and experience the benefits firsthand. If you're interested in learning more or discussing licensing options, please don't hesitate to reach out to us at [email protected]

Thank you for your interest, and we look forward to helping you revolutionize your browser automation experience!

I recently used Ruffle [2] to get some Flash applications [0] working in the Pro version of my web browser [1], which is specifically designed to be remotely accessible and embeddable in an iframe. To run Ruffle on pages that require it, I utilize the Chrome Remote Debugging Protocol [3], similar to how a Chrome extension content script operates. Ruffle itself relies on WebAssembly and runs smoothly. It's been exciting to see the audio and video functionality of these old games restored and being able to play them again.

-

[0]: https://github.com/ruffle-rs/ruffle/wiki/Test-SWFs

[1]: https://github.com/crisdosyago/BrowserBox#bb-pro-vs-regular-...

[2]: https://github.com/ruffle-rs/ruffle

[3]: https://chromedevtools.github.io/devtools-protocol/tot/