| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
For some reason with Google Chrome 70 this is not the case any more.
|
|
Commit 7730e0d64ec895091a0dd7eb0e3c6ce2ed02d981 removed logging to WARC
files. Add it again, but with a different implementation.. Credits to
structlog for inspiration.
|
|
Judging from the docs this is the proper way to store these resources.
Enable both for the IRC bot by default, since they won’t interfere with
IA’s wayback machine.
|
|
|
|
This is mainly a quality of life change
|
|
Previously a browser crash stalled the entire grab, since events from
pychrome were handled asynchronously in a different thread and
exceptions were not propagated to the main thread.
Now all browser events are stored in a queue and processed by the main
thread, allowing us to handle browser crashes gracefully (more or less).
This made the following additional changes necessary:
- Clear separation between producer (browser) and consumer (WARC, stats,
…)
- Behavior scripts now yield events as well, instead of accessing the
WARC writer
- WARC logging was removed (for now) and WARC writer does not require
serialization any more
|
|
Otherwise it may clash with symbols defined by the page.
|
|
|
|
…and not just the current viewport. Due to limitations within Chrome it
may be necessary to manually stitch multiple images if the page height
exceeds 16k pixels.
|
|
Configureable. Clicks elements matching one (or more) CSS selectors once
or multiple times.
Currently supported: Facebook, Twitter, Disqus (embedded iframe)
|
|
The “load more” button does not exist any more.
|
|
No functional changes, just cleanup. Replaces onload and onsnapshot
events. Move screen metric emulation, DOM snapshots and screenshots here
as well.
|
|
|
