As our caching options became more flexible and caching is an integral part of Rendertron we would like to introduce a different way of handling cache configuration.

Currently, the cache configuration is cache and can either be null, datastore or memory.

The goals of this issue are:

• Change the [cache property](https://github.com/GoogleChrome/rendertron/blob/0ed866fa98b31884289

What is the current behavior?

Crawling a website that uses # (hashes) for url navigation does not crawl the pages that use #

The urls using # are not followed.

If the current behavior is a bug, please provide the steps to reproduce

Try crawling a website like mykita.com/en/

What is the motivation / use case for changing the behavior?

Though hashes are not ment to chan

URL:- https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html
The below code snippet is not coming in the output pdf.
mvn --version
However, another code snippet appearing properly
Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19 14:51:28+0100)
![image](https://user-images.githubusercontent.com/354596/47339163-16508d00-d6e6-11e8-872b-a1f10d96d55

🐛 Bug Report

Using jest-dev-server, set a command like:

module.exports = {
  command: 'npm run start',
  launchTimeout: 1000,
}

If the timeout occurs, you get this message:

Server has taken more than 1000ms to start.

The problem here is that jest-dev-server then never sends the proper signals to the processes started by the command, meaning they get

Also, it's not "@apify/httpRequest" package but "@apify/http-request"

如题，mac电脑最新版chrome跑的

https://github.com/GoogleChrome/puppeteer/blob/v1.11.0/docs/api.md#class-coverage

Coverage gathers information about parts of JavaScript and CSS that were used by the page.

An example of using JavaScript and CSS coverage to get percentage of initially executed code:

// Enable both JavaScript and CSS coverage
await Promise.all([
  page.coverage.startJSCoverage(),
  page.coverage.

To get a better impression of the final images, could you please add the generated documents in the tests to the repo?

I have read the docs but seeing final results could give a better first impression.

For example I'd like to see:

• header an footer styles
• a complex microsoft word document converted to pdf

What are the limits to the conversion process, e.g. when rendering footnotes

https://github.com/GoogleChromeLabs/puppeteer-examples/blob/master/lazyimages_without_scroll_events.js#L110

i have doubts screenshotPageWithoutScroll :

• it is using DEFAULT_VIEWPORT which is may be vary for each page, with long content page, some part of the page will not exists on the viewport, this causing IntersectionObserver not triggered, and make the test FAILED
• For example

Steps to repro:

Run the command from documentation
docker run --net=host -v ./CONFIG_FILE.yaml:/etc/rendora/config.yaml rendora/rendora

What I have tried:

1. git clone repo && cd to config_examples && run with docker run --net=host -v ./CONFIG_FILE.yaml:/etc/rendora/config.yaml rendora/rendora
   Return value is
   docker: Error response from daemon: create ./CONFIG_FILE.yaml: "./CONFIG_

Points to cover:

• playbook for how to get started with testing
• differences between testing locally vs staging vs production
• how to configure tests for different environments

@johngrimsey thank you for the idea! Please feel free to comment if I missed something.

Change the action for CA2200 on the ruleset file to Error, and make the solution build

Issue
When using SingleBrowserImplementation and chrome gets into a state in which it cannot be restarted then the error does not bubble which causes a javascript unhandledrejection. Since there is no way to catch this it forces consuming code into a dead end. Using node v8.11.1

Reproduction:
I have not found a way to put chrome into such a state that it cannot be restarted so the rep

Some prior art here:

https://github.com/puppeteer/examples/blob/master/verify_sw_caching.js
https://michaljanaszek.com/blog/test-website-performance-with-puppeteer/#cacheAndServiceWorker

Implementation of puppeteer clip functionality.
Example:

{
    clip: {
        x: 10,
        y: 30,
        height: 300,
        width: 200
    }
}

• x - <number> - x-coordinate of top-left corner of clip area;
• y - <number> - y-coordinate of top-left corner of clip area