Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add CHROME_TIMEOUT args #1120

Merged
merged 2 commits into from
Mar 15, 2023
Merged

add CHROME_TIMEOUT args #1120

merged 2 commits into from
Mar 15, 2023

Conversation

fa0311
Copy link
Contributor

@fa0311 fa0311 commented Mar 14, 2023

Summary

  • add CHROME_TIMEOUT args

Environment

Chromium 111.0.5563.64 snap

Why

Chromium --timeout argument doesn't actually do timeout behavior.
For example, when --screenshot argument is given, it delays the shooting for the time specified by the timeout.
Not sure if this behavior is caused by chromium v111.

Note

CHROME_TIMEOUT is set to 0 by default.
For example, when --screenshot argument is given, If timeout is set to 0, the image is captured at the same time DOMContentLoaded fires, so some Web sites may not be captured as intended.
When set to 1 or higher, the possibility of getting the desired photo increases dramatically.

Related

606fa39

Changes these areas

  • Bugfixes
  • Feature behavior
  • Command line interface
  • Configuration options
  • Internal architecture
  • Snapshot data layout on disk

@pirate
Copy link
Member

pirate commented Mar 15, 2023

Thanks!

I confirmed it seems to be a recent change they made: https://developer.chrome.com/articles/new-headless/

@pirate pirate merged commit f5e631d into ArchiveBox:dev Mar 15, 2023
@fa0311
Copy link
Contributor Author

fa0311 commented Mar 16, 2023

I confirmed it seems to be a recent change they made: https://developer.chrome.com/articles/new-headless/

This seems to be implemented in v112, so it doesn't seem to affect v111, but v111 seems to be unstable due to this.
For example, --window-size does not work,

@fa0311
Copy link
Contributor Author

fa0311 commented Mar 16, 2023

I have set up Issues regarding this. #1122

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants