121–130 of 133 posts
Earlier quoted context omitted.
Can't you only have one profile open at a time, and each one is linked to a different Google account? Firefox allows you to have each tab open in a different container, and they don't have to be tied to anything in particular. I can have different tabs open to the AWS console for each AWS account I use. I can also switch tabs to change between different user accounts to test interactions between users on the site I'm…
> Can't you only have one profile open at a time No. Each profile opens in a new Chrome window. You can have as many open as you'd like. > and each one is linked to a different Google account? No. Local profiles have always been a thing. Chrome's implementation has better UX for privacy IMHO; it's harder to accidentally open a tab in a different profile than expected, which I do _all the time_ in Firefox. In Chrome,…
Earlier quoted context omitted.
Did you have a reason to not use PDFium directly?
Can you recommend any resources for getting started with pdfium?
Earlier quoted context omitted.
Selenium feels old and outdated, it's always a hustle to install it/get it running and I have to use WebdriverIO with it in Node. I tried Puppeteer a few days ago, I just did `npm i puppeteer` and it worked as expected.
How would you describe the npm install process?
Earlier quoted context omitted.
How would you describe the npm install process?
Simple, 0 configuration, fast. With a new installation of Selenium I always have to download the Firefox/Chrome drivers, have to setup paths, debug startup erros, plus it crashes pretty often.
Earlier quoted context omitted.
How would you describe the npm install process?
Just like any other module, but slower. There's a substantial bag of bits it needs to fetch (chromium), but that's cached. I've also noticed that sometimes (in CI, less than 5% of the runs) the installation or run will fail deep in chromium. It's actually spawning a chrome process and tunneling remote commands to the child process to do work, so, I guess the flakiness is (almost) excusable? Restarting the test always…
Earlier quoted context omitted.
Does puppeteer work with Safari and MS browsers or is it another Chrome only tool (and now Firefox)?
It's yet another Chrome only tool.
Earlier quoted context omitted.
How would you describe the npm install process?
Simple, 0 configuration, fast. With a new installation of Selenium I always have to download the Firefox/Chrome drivers, have to setup paths, debug startup erros, plus it crashes pretty often.
For anybody who wants to follow along, the Firefox work is tracked here: https://gitter.im/webhintio/Firefox The experiment was a great start to see what is needed to support Puppeteer. The next step is coming up with a well-integrated architecture. Find me on the web to talk to me about your use cases and ideas for Puppeteer.
In case you're wondering, and the linked page doesn't explain: > Puppeteer is a Node library which provides a high-level API to control headless Chrome or Chromium over the DevTools Protocol. It can also be configured to use full (non-headless) Chrome or Chromium. https://developers.google.com/web/tools/puppeteer/
I always find it weird that people constantly try to "sell" me (us) something but never tell me what that thing is or why I want it.
Then it gets upvoted to a more general audience, who ask "Puppeteer? what's that?"