chromiumoxide VS rust-headless-chrome

Re rust-headless-chrome: yes, being handwritten it probably has a nicer API/DX but is missing some features. I would give it a go if you are struggling with chromiumoxide. The flakoness could be due to chromiumoxide going faster than the browser, ie trying to get elements before they have loaded. Most web automation tools will have ways to slow down themselves down, eg wait for 1 second, or keep checking whether an element exists. This is what things like Playwright provide, not sure what chomiumoxide does. Also not sure if this is something that is part of the devtools spec and thus should already be in chomiumoxide, or features implemented on top, in which case chomiumoxide might not have it (though I suspect it probably does) eg see https://github.com/mattsse/chromiumoxide/issues/42 In hindsight chomiumoxide might not be the best choice for you if it is lacking these kinds of features. I'm just using it for executing Javascript, not acually interacting with the Dom. I prefer it because I think the codegen approach is best and is the project most likely to succeed long term.

Adding a ton of new features for the headless chrome api chromiumoxide, especially javascript evaluation functions. Also started implementing a test suite.

I'm using this to fill forms interactively and emulate a user. https://github.com/rust-headless-chrome/rust-headless-chrome

Afaict, it drives a stock Chromium instance. I'm not sure how Fidelity is detecting it, but they detect it even in normal headful mode. Idk if there's some JS that notices there's no mouse-move movements.

It's just not worth the headache. I despise bending over backwards for companies like this. But obviously I have no choice since they're my 401k plan facilitator.

Thanks, I was looking into that as well and got their example up and running. I also saw that chromiumoxide mentions rust-headless-chrome in its references section in the README, which is also updated recently, any differences between the two? Seems like chromiumoxide is async with code gen whereas rust-headless-chrome is not, is that right?

mdBook allows you to create book from markdown files. It's pretty much alike Gitbook but implemented in Rust. However, unlike Gitbook that supports using calibre for generating PDF, for a long time, mdBook doesn't support generating PDF files natively, and supporting that is also not in their roadmap. Existing plugins (backends) such as mdbook-latex that utilize Tectonic as well as pandoc solutions will generate a PDF page that doesn't unify with the existing mdBook generated HTML version. Considering these facts, I created a mdBook backend named mdbook-pdf for generating PDF based on headless chrome and Chrome DevTools Protocol Page.printToPDF.

There's https://github.com/stevepryde/thirtyfour for Selenium, and https://github.com/atroche/rust-headless-chrome for Chromium.

I published headless-chrome a few years ago, but I haven't cut a new release in almost two years now — despite the issues and pull requests piling up. I'm not relying on it for my work like I was previously, and I just don't have the spare energy to be a good maintainer.