Prototype: Puppeteer for Firefox • Hacker News Board

Re: Prototype: Puppeteer for Firefox

#31

Post by Congeec » Tue, Jul 23, 2019, 10:33 AM UTC

nicoburns wrote: post #25

rehemiau wrote: post #19

How is the DevTools/Remote protocol better (or worse) than WebDriver prptocol for integration testing?

It's much more reliable.

How? With selenium I have a case that WebElement.click() fails but it doesn’t throw. Also Select(...).select_by_visible_text() throws WebDriverException, StaleElementException, etc even if you WebDriverWait()’d for it to be available. To me these show selenium is unreliable. How puppeteer is reliable pertaining to these cases?

Re: Prototype: Puppeteer for Firefox

#32

Post by Zardoz84 » Tue, Jul 23, 2019, 10:38 AM UTC

Crinus wrote: post #16

trishmapow2 wrote: post #12

Earlier quoted context omitted.

Interesting, I thought Firefox usage would be increasing based on all the hype/people converting on HN/other tech websites but the market share is actually falling. Guess it puts into perspective the size of that cohort compared to the rest of the world.

After Firefox broke most extensions with their removal of XUL extensions and embrace of "WebExtensions" (aka Chrome extensions), it lost a major differentiation point from Chrome. People simply have no (immediate, practical) reason to use Firefox. Back in the Mozilla days i was using Mozilla because it was very powerful and flexible despite being very slow (i remember watching Mozilla 0.6's dialog boxes draw themselv…

Firefox actually is FASTER that Chrome. Also, if you have any privacy concerns, you should stop using Chrome ASAP.

Re: Prototype: Puppeteer for Firefox

#33

Post by daveFNbuck » Tue, Jul 23, 2019, 10:38 AM UTC

blodovnik wrote: post #26

Firefox has lost its lead because it's lost the developers. Chrome has invested massively in developer tools for chrome and it's shows.... I think chrome is the best software ever written. The developer tools are so powerful that it'd hard to even know the full breadth of what's in there. Firefox offers nothing to developers over chrome, which is sad.

> Firefox offers nothing to developers over chrome, which is sad.

Firefox has multi-account containers. Having different tabs logged in to different accounts is huge for me.

Re: Prototype: Puppeteer for Firefox

#34

Post by ozim » Tue, Jul 23, 2019, 10:39 AM UTC

sebazzz wrote: post #15

For automated testing, why Puppeteer instead of Selenium?

I am done with selenium because you cannot make stable tests. They are always flaky.

Re: Prototype: Puppeteer for Firefox

#35

Post by Zardoz84 » Tue, Jul 23, 2019, 10:41 AM UTC

blodovnik wrote: post #26

Firefox has lost its lead because it's lost the developers. Chrome has invested massively in developer tools for chrome and it's shows.... I think chrome is the best software ever written. The developer tools are so powerful that it'd hard to even know the full breadth of what's in there. Firefox offers nothing to developers over chrome, which is sad.

You actually try FF dev tools ?

Re: Prototype: Puppeteer for Firefox

#36

Post by kyriakos » Tue, Jul 23, 2019, 10:41 AM UTC

How's pdf rendering in Firefox? Chrome headless has its issues with headers and footers

Re: Prototype: Puppeteer for Firefox

#37

Post by HunOL » Tue, Jul 23, 2019, 10:51 AM UTC

d33 wrote: post #17

sebazzz wrote: post #15

For automated testing, why Puppeteer instead of Selenium?

Much better access to low-level information. You can hook (and mock) requests, see what POST data was sent and basically do lots of magic. Also, my experience with Selenium under Python is that doing anything bigger quickly turns into one giant timing hack.

If it really E2E from user perspective you shouldn't doing any magic and manipulate POST data.

Re: Prototype: Puppeteer for Firefox

#38

Post by fsiefken » Tue, Jul 23, 2019, 10:53 AM UTC

pmontra wrote: post #13

fsiefken wrote: post #4

is there a benefit to using firefox with puppeteer compared to chromium and puppeteer? or is it just a matter of choice and being able to also use firefox for automated testing?

I run integration tests in Ruby on Rails with Capybara using both the Chrome and Firefox drivers. That project was stopped for a while and when I went back to it the Firefox driver didn't work anymore. I didn't have the time to check what went wrong and fix it but I'm developing with Firefox anyway. I think it's important to test with the major browsers. My customer didn't ask about IE. I remember when I had a few VM…

Ah yes, browser compatibility! IE will soon be chromium-webkit based.

Re: Prototype: Puppeteer for Firefox

#39

Post by mjepronk » Tue, Jul 23, 2019, 10:53 AM UTC

kyriakos wrote: post #36

How's pdf rendering in Firefox? Chrome headless has its issues with headers and footers

It's good, however it's not possible to use the remote debugging protocol for printing to PDF yet.

Re: Prototype: Puppeteer for Firefox

#40

Post by gryffin » Tue, Jul 23, 2019, 10:57 AM UTC

kyriakos wrote: post #36

How's pdf rendering in Firefox? Chrome headless has its issues with headers and footers

Firefox uses PDF.js[1] to render pdf. This is a standalone project to render pdf in the browser using html and js. If I remember correctly, you can even render pdf in chrome using this.

[1]https://mozilla.github.io/pdf.js/