[GH-ISSUE #1122] Feature Request: Explicitly specify --headless=new #704

Closed
opened 2026-03-01 14:45:38 +03:00 by kerem · 2 comments
Owner

Originally created by @fa0311 on GitHub (Mar 16, 2023).
Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/1122

Type

  • General question or discussion
  • Propose a brand new feature
  • Request modification of existing behavior or design

What is the problem that your feature request solves

Resolve the problem of unstable headless mode in the current chromium v111.
For example, it can solve the problem of RESOLUTION (--window-size) not working.

Describe the ideal specific solution you'd want, and whether it fits into any broader scope of changes

Change the argument given to chromium to --headless=new

Note

$ /usr/bin/chromium-browser --version
Chromium 111.0.5563.64 snap
Command Img
/usr/bin/chromium-browser --headless --timeout=2000 --screenshot --window-size=1440,2000 https://github.com/ArchiveBox/ screenshot1
/usr/bin/chromium-browser --headless=new --timeout=2000 --screenshot --window-size=1440,2000 https://github.com/ArchiveBox/ screenshot

  • I'm willing to contribute dev time to fix this issue
Originally created by @fa0311 on GitHub (Mar 16, 2023). Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/1122 ## Type - [ ] General question or discussion - [ ] Propose a brand new feature - [x] Request modification of existing behavior or design ## What is the problem that your feature request solves Resolve the problem of unstable headless mode in the current chromium v111. For example, it can solve the problem of `RESOLUTION` (`--window-size`) not working. ## Describe the ideal specific solution you'd want, and whether it fits into any broader scope of changes Change the argument given to chromium to `--headless=new` ## Note ```sh $ /usr/bin/chromium-browser --version Chromium 111.0.5563.64 snap ``` | Command | Img | | --- | --- | | `/usr/bin/chromium-browser --headless --timeout=2000 --screenshot --window-size=1440,2000 https://github.com/ArchiveBox/` | ![screenshot1](https://user-images.githubusercontent.com/34892635/225538544-40403f7f-216e-4fd4-9ddd-fa2c60d384a6.png) | | `/usr/bin/chromium-browser --headless=new --timeout=2000 --screenshot --window-size=1440,2000 https://github.com/ArchiveBox/` | ![screenshot](https://user-images.githubusercontent.com/34892635/225538553-6f8607cf-cd9a-408d-9efa-75022462fff9.png) | --- - [x] I'm willing to contribute [dev time](https://github.com/ArchiveBox/ArchiveBox#archivebox-development) to fix this issue
Author
Owner

@pirate commented on GitHub (Mar 16, 2023):

Want to open a PR so you get the credit 😉 ? I'm also happy to do it

We just have to add a version check and if the version is >= 111 change the argument

<!-- gh-comment-id:1471461770 --> @pirate commented on GitHub (Mar 16, 2023): Want to open a PR so you get the credit 😉 ? I'm also happy to do it We just have to add a version check and if the version is >= 111 change the argument
Author
Owner

@pirate commented on GitHub (Jun 13, 2023):

closing because PR was merged, thanks again!

<!-- gh-comment-id:1589156856 --> @pirate commented on GitHub (Jun 13, 2023): closing because PR was merged, thanks again!
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/ArchiveBox#704
No description provided.