31–39 of 39 posts
Two things: 1. Please do not test a web app with Chrome only, we don't want to go back to a world with a single browser 2. > So, until puppeteer supports this, we will rely on jsdom, a package available via npm JSDOM is not just a package on npm, it's an engineering piece of art
I have given up on Firefox. Every bug I submit takes it own sweet time to get fixed.
I got able to make it run inside a docker.
In this exact moment the example at the repo is just returning a blank PDF but the problem is at the API Gateway.
Where I work we prefer jQuery to the native DOM API for scraping. It really speeds up the process of extracting data. For example with Puppeteer you can do page.injectFile("jquery-3.2.1.min.js"). I think that would simplify your evaluate() calls. It would also be easy to speed up the whole process by doing a single evaluate() call per page with all your scraping code in it. BTW we just released an article with tips &…
Two things: 1. Please do not test a web app with Chrome only, we don't want to go back to a world with a single browser 2. > So, until puppeteer supports this, we will rely on jsdom, a package available via npm JSDOM is not just a package on npm, it's an engineering piece of art
I hope Puppeteer become a standard.
> Since the official announcement of Chrome Headless, many of the industry standard libraries for automated testing have been discontinued by their maintainers. The prominent of these are PhantomJS and Selenium IDE for Firefox. Correct me if I'm wrong, but if I'm notm mistaken Selenium IDE has been discontinued due to lack of mantainers, and that has little if any relation to Chrome Headless. The IDE is just a more e…
Earlier quoted context omitted.
You should be able to use a data URI containing the HTML string
It's not allowed anymore: https://groups.google.com/a/chromium.org/forum/m/#!topic/bli...
Initial assumption when reading the thread was that navigating to a data URI would be handled like entry of a data URI into the omnibox and still be allowed.
A small test case confirms that assumption - it works.
Two things: 1. Please do not test a web app with Chrome only, we don't want to go back to a world with a single browser 2. > So, until puppeteer supports this, we will rely on jsdom, a package available via npm JSDOM is not just a package on npm, it's an engineering piece of art