<h2class="anchor anchorWithStickyNavbar_LWe7"id="q-who-maintains-puppeteer">Q: Who maintains Puppeteer?<ahref="#q-who-maintains-puppeteer"class="hash-link"aria-label="Direct link to Q: Who maintains Puppeteer?"title="Direct link to Q: Who maintains Puppeteer?"></a></h2>
<p>The Chrome DevTools team maintains the library, but we'd love your help and
<h2class="anchor anchorWithStickyNavbar_LWe7"id="q-what-is-the-status-of-cross-browser-support">Q: What is the status of cross-browser support?<ahref="#q-what-is-the-status-of-cross-browser-support"class="hash-link"aria-label="Direct link to Q: What is the status of cross-browser support?"title="Direct link to Q: What is the status of cross-browser support?"></a></h2>
<p>Official Firefox support is currently experimental. The ongoing collaboration
non-standard DevTools Protocol used by Chrome).</p>
<h2class="anchor anchorWithStickyNavbar_LWe7"id="q-what-are-puppeteers-goals-and-principles">Q: What are Puppeteer’s goals and principles?<ahref="#q-what-are-puppeteers-goals-and-principles"class="hash-link"aria-label="Direct link to Q: What are Puppeteer’s goals and principles?"title="Direct link to Q: What are Puppeteer’s goals and principles?"></a></h2>
<p>The goals of the project are:</p>
<ul>
<li>Provide a slim, canonical library that highlights the capabilities of the
<li><strong>Speed</strong>: Puppeteer has almost zero performance overhead over an automated
page.</li>
<li><strong>Security</strong>: Puppeteer operates off-process with respect to Chromium, making
it safe to automate potentially malicious pages.</li>
<li><strong>Stability</strong>: Puppeteer should not be flaky and should not leak memory.</li>
<li><strong>Simplicity</strong>: Puppeteer provides a high-level API that’s easy to use,
understand, and debug.</li>
</ul>
<h2class="anchor anchorWithStickyNavbar_LWe7"id="q-is-puppeteer-replacing-seleniumwebdriver">Q: Is Puppeteer replacing Selenium/WebDriver?<ahref="#q-is-puppeteer-replacing-seleniumwebdriver"class="hash-link"aria-label="Direct link to Q: Is Puppeteer replacing Selenium/WebDriver?"title="Direct link to Q: Is Puppeteer replacing Selenium/WebDriver?"></a></h2>
<p><strong>No</strong>. Both projects are valuable for very different reasons:</p>
<ul>
<li>Selenium/WebDriver focuses on cross-browser automation; its value proposition
is a single standard API that works across all major browsers.</li>
<li>Puppeteer focuses on Chromium; its value proposition is richer functionality
and higher reliability.</li>
</ul>
<p>That said, you <strong>can</strong> use Puppeteer to run tests against Chromium, e.g. using
Chrome DevTools to inspect the test environment.</li>
</ul>
<h2class="anchor anchorWithStickyNavbar_LWe7"id="q-why-doesnt-puppeteer-vxxx-work-with-chromium-vyyy">Q: Why doesn’t Puppeteer v.XXX work with Chromium v.YYY?<ahref="#q-why-doesnt-puppeteer-vxxx-work-with-chromium-vyyy"class="hash-link"aria-label="Direct link to Q: Why doesn’t Puppeteer v.XXX work with Chromium v.YYY?"title="Direct link to Q: Why doesn’t Puppeteer v.XXX work with Chromium v.YYY?"></a></h2>
<p>We see Puppeteer as an <strong>indivisible entity</strong> with Chromium. Each version of
<li>It turned out this is an issue with the DevTools protocol, so we’re fixing it
in Chromium: <ahref="https://chromium-review.googlesource.com/c/chromium/src/+/1102154"target="_blank"rel="noopener noreferrer">https://chromium-review.googlesource.com/c/chromium/src/+/1102154</a></li>
<li>Once the upstream fix is landed, we roll updated Chromium into Puppeteer:
<h2class="anchor anchorWithStickyNavbar_LWe7"id="q-which-chrome-version-does-puppeteer-use">Q: Which Chrome version does Puppeteer use?<ahref="#q-which-chrome-version-does-puppeteer-use"class="hash-link"aria-label="Direct link to Q: Which Chrome version does Puppeteer use?"title="Direct link to Q: Which Chrome version does Puppeteer use?"></a></h2>
<h2class="anchor anchorWithStickyNavbar_LWe7"id="q-which-firefox-version-does-puppeteer-use">Q: Which Firefox version does Puppeteer use?<ahref="#q-which-firefox-version-does-puppeteer-use"class="hash-link"aria-label="Direct link to Q: Which Firefox version does Puppeteer use?"title="Direct link to Q: Which Firefox version does Puppeteer use?"></a></h2>
<p>Since Firefox support is experimental, Puppeteer downloads the latest
<h4class="anchor anchorWithStickyNavbar_LWe7"id="q-whats-considered-a-navigation">Q: What’s considered a “Navigation”?<ahref="#q-whats-considered-a-navigation"class="hash-link"aria-label="Direct link to Q: What’s considered a “Navigation”?"title="Direct link to Q: What’s considered a “Navigation”?"></a></h4>
<p>From Puppeteer’s standpoint, <strong>“navigation” is anything that changes a page’s
<p>With this definition of “navigation,” <strong>Puppeteer works seamlessly with
single-page applications.</strong></p>
<h4class="anchor anchorWithStickyNavbar_LWe7"id="q-whats-the-difference-between-a-trusted-and-untrusted-input-event">Q: What’s the difference between a “trusted" and "untrusted" input event?<ahref="#q-whats-the-difference-between-a-trusted-and-untrusted-input-event"class="hash-link"aria-label="Direct link to Q: What’s the difference between a “trusted" and "untrusted" input event?"title="Direct link to Q: What’s the difference between a “trusted" and "untrusted" input event?"></a></h4>
<p>In browsers, input events could be divided into two big groups: trusted vs.
untrusted.</p>
<ul>
<li><strong>Trusted events</strong>: events generated by users interacting with the page, e.g.
using a mouse or keyboard.</li>
<li><strong>Untrusted event</strong>: events generated by Web APIs, e.g. <code>document.createEvent</code>
or <code>element.click()</code> methods.</li>
</ul>
<p>Websites can distinguish between these two groups:</p>
<h4class="anchor anchorWithStickyNavbar_LWe7"id="q-what-features-does-puppeteer-not-support">Q: What features does Puppeteer not support?<ahref="#q-what-features-does-puppeteer-not-support"class="hash-link"aria-label="Direct link to Q: What features does Puppeteer not support?"title="Direct link to Q: What features does Puppeteer not support?"></a></h4>
<p>You may find that Puppeteer does not behave as expected when controlling pages
<li>Puppeteer is bundled with <ahref="https://developer.chrome.com/blog/chrome-for-testing/"target="_blank"rel="noopener noreferrer">Chrome for Testing</a> — not the regular Chrome — and so by default, it
<ahref="https://caniuse.com/#feat=http-live-streaming"target="_blank"rel="noopener noreferrer">does not support HTTP Live Streaming (HLS)</a>.</li>
</ul>
<h4class="anchor anchorWithStickyNavbar_LWe7"id="q-i-am-having-trouble-installing--running-puppeteer-in-my-test-environment-where-should-i-look-for-help">Q: I am having trouble installing / running Puppeteer in my test environment. Where should I look for help?<ahref="#q-i-am-having-trouble-installing--running-puppeteer-in-my-test-environment-where-should-i-look-for-help"class="hash-link"aria-label="Direct link to Q: I am having trouble installing / running Puppeteer in my test environment. Where should I look for help?"title="Direct link to Q: I am having trouble installing / running Puppeteer in my test environment. Where should I look for help?"></a></h4>
guide for various operating systems that lists the required dependencies.</p>
<h4class="anchor anchorWithStickyNavbar_LWe7"id="q-i-have-more-questions-where-do-i-ask">Q: I have more questions! Where do I ask?<ahref="#q-i-have-more-questions-where-do-i-ask"class="hash-link"aria-label="Direct link to Q: I have more questions! Where do I ask?"title="Direct link to Q: I have more questions! Where do I ask?"></a></h4>
<p>There are many ways to get help on Puppeteer:</p>
