Can't use getDisplayMedia (and then start recording) in headless mode

Steps to reproduce

Tell us about your environment:

• Puppeteer version: 1.15.0
• Platform / OS version: Ubuntu 16.04
• URLs (if applicable):
• Node.js version: v10.15.3

What steps will reproduce the problem?

Please include code that reproduces the issue.

1. Run the following code, set headless to true or false and see the difference.

const puppeteer = require('puppeteer')

;(async () => {
  const url = 'https://www.google.com'
  const browser = await puppeteer.launch({
    headless: false,
    args: [
      `--window-size=1920,1080`,
      '--enable-experimental-web-platform-features',
      '--disable-infobars',
      '--enable-usermedia-screen-capturing',
      '--allow-http-screen-capture',
      '--auto-select-desktop-capture-source=webclip',
      '--ignore-certificate-errors', 
       '--unsafely-treat-insecure-origin-as-secure=' + url
    ]
  });
  const page = await browser.newPage()
  await page.setViewport({
    width: 1920,
    height: 1080,
  })
  await page.goto(url)
  page.evaluate(async () => {
    document.title = 'webclip'
    const stream = await navigator.mediaDevices.getDisplayMedia({ video: true })
    const recorder = new window.MediaRecorder(stream, { mimeType: 'video/webm' })
    recorder.start(10)
    const chunks = []
    recorder.addEventListener('dataavailable', event => {
      if (event.data && event.data.size) {
        chunks.push(event.data)
      }
    })
  })
})()

What is the expected result? Maybe it should start recording (I don’t know whether this behavior is intended and I haven’t found percisely related information).

What happens instead? Throw exceptions.

[crisdosyago]

@ldenoue no. pretty much likely that it can’t. The bug I linked above is now assigned to [e-mail]

Go star the issue and spread the world to show it’s important. That contributes to the Chrome team’s decisions about what to work on next.

[thegiantbeast]

Just in case someone might miss this, the new CRBUG is: https://bugs.chromium.org/p/chromium/issues/detail?id=1268342

This should be fixed because having to run the full chrome instance because of getDisplayMedia isn’t the kind of behaviour I would expect from the headless mode 🤔