3 ms·
I think simple-headless-chrome is more far along https://github.com/LucianoGanga/simple-headless-chrome https://github.com/LucianoGanga/simple-headless-chrome
by Akujin 9y ago
I think simple-headless-chrome is more far along
https://github.com/LucianoGanga/simple-headless-chrome https://github.com/LucianoGanga/simple-headless-chrome
- paulirish 9y agoWe're fans of LucianoGanga's project (and of Chromeless, Doffy, Chrominator, Chromy, Navalia). I can tell you from personal experience that dealing with the raw DevTools Protocol isn't ideal for a developer writing an automation script, so it's clear there's demand for libraries with this higher-level API. Would love to know if there's a feature parity concern you have or what you'd like to see from puppeteer (or any of these projects). (My personal feature unicorn: generate not a static screenshot but a proper video of a page session)
- malsheikh 9y agoChromeless allows for the setting of cookies. I noticed in an issue for Puppeteer that it wasn't seen as a high priority. Our use-case (session based cookies) rely on a cookie being set in order for our PDF screenshots to work. Any chance you could give us some insight on when this may be available?
- Akujin 9y agoWe're mainly using these things for screenshots of existing corporate intranet tools that are then surfaced to slack. Headless chrome is finally giving us screenshots that are actually authentically what you would actually see on the screen. PhantomJS came close but still has issues.
- Akujin 9y agoYour unicorn would be lovely though :D
- lucho_1312 9y agoHi @paulirish! I started with your unicorn haha, I wrote only a few lines of code, to use the screencast events to save the frames of a page. Here's the branch with that: https://github.com/LucianoGanga/simple-headless-chrome/tree/screencast https://github.com/LucianoGanga/simple-headless-chrome/tree/... And here is the thread I'm gonna use to discuss this: https://github.com/LucianoGanga/simple-headless-chrome/issues/65 https://github.com/LucianoGanga/simple-headless-chrome/issue... If someone has an idea of what the "ideal implementation" would look like, I'd really appreciate it!