Open
Bug 1453229
Opened 6 years ago
Updated 1 year ago
headless option to save URL page source
Categories
(Firefox :: Headless, enhancement, P5)
Tracking
()
UNCONFIRMED
People
(Reporter: bcoulam, Unassigned)
References
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:59.0) Gecko/20100101 Firefox/59.0 Build ID: 20180323154952 Steps to reproduce: I read Mozilla dev docs on command line options and headless mode. Found comment from Brendan Dahl that firefox does not have a command line option to save page source and encouraged the OP to request the feature request. Attempted invoking firefox headless anyway looking for option to save page source, to no avail. Actual results: Nothing, as there is no command line option to save page source. For reference, headless Chrome has this option if you use --dump-dom and redirect output to a file. Expected results: Headless Firefox should provide a command line option to save the given URL's page source (the HTML ultimately delivered after all the handshakes, security, cookies, crumbs, etc have been negotiated and dealt with). Ideally the -P option to use a given user profile when GETing a URL should be an option for headless as well to inherit all the goodness cached in the given profile that contains the cookies, certs, crumbs, etc required by the target URL.
Reporter | ||
Comment 1•6 years ago
|
||
Sorry this was entered as a bug. I'm new. Could not find an option to enter a feature request. The Brendan Dahl post where the bits about saving page source are found near the bottom of the comments: https://adriftwith.me/coding/2017/04/21/headless-slimerjs-with-firefox/
Updated•6 years ago
|
Priority: -- → P5
Comment 2•6 years ago
|
||
The above adriftwith.me blog post by bdahl suggests that headless bugs should be filed with Component=Headless Also this bug can be a dependency of the headless meta bug 1338004
Such a --dump-dom might also require something like --virtual-time-budget in Chromium to wait before dumping
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•