31–40 of 88 posts
Anyone know if this supports audio playback?
Edit: looking at the code, it will work just fine, and that means I can even use it myself to run Firefox's unit and integration tests, I usually use xvfb on Linux.
"headless" Poke me when there are no X11/Qt/GTK/whatever dependencies at all - that is headless. https://packages.debian.org/stretch/firefox-esr
I doubt it'll happen anytime too soon, but Mozilla should see the community interest.
So I can navigate by cardinal directions now (like scrolling south a bit)? Joke aside: can somone explain "headless" to me here?
When you run the browser, but it doesn't actually display anything on screen. Uses include rendering a screenshot (e.g. a preview thumbnail) of some website on a server, or running automated UI tests that click around a web app and fill out forms to verify its functionality.
I was wondering if I could use this (using a plugin) or Chrome to generate PDF files on the web server. Most of the PDF generation software out there are quite expensive.
This feels a little nicer than Selenium as it's one less layer of abstraction.
EDIT: guess from other comments WebDriver is the right method to access.
I was wondering if I could use this (using a plugin) or Chrome to generate PDF files on the web server. Most of the PDF generation software out there are quite expensive.
Maybe it's possible with the print option Chrome offers. Regular Chrome can print to PDF files. Maybe headless Chrome supports that. Edit: It's possible. It's on the introduction page of Chrome Headless https://developers.google.com/web/updates/2017/04/headless-c... Look at 'Create a PDF'
What are the biggest challenges when implementing headless mode? I'm asking cause this feature took some time to be delivered both in Firefox and Chrome and I always assumed that it should be 'pretty' straightforward to implement. Is it that both engines were coupled with GUI libs?
What are the biggest challenges when implementing headless mode? I'm asking cause this feature took some time to be delivered both in Firefox and Chrome and I always assumed that it should be 'pretty' straightforward to implement. Is it that both engines were coupled with GUI libs?