UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36

Steps to reproduce the problem:
1. Run Headless Chrome (v71):

/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --headless --disable-gpu --remote-debugging-port=9222

2. Running following node script against it:

const CDP = require("chrome-remote-interface");

async function testCreateBrowserContext() {
  const client = await CDP({ port: 9222 });
  try {
    // Set up the client.
    await client.Page.enable();
    await client.DOM.enable();

   // let browserContext = await client.send("Target.createBrowserContext", { });
    var browserContext = await client.Target.createBrowserContext({});

    let target = await client.Target.createTarget({url: "about:blank", browserContextId: browserContext.browserContextId});
    console.log("New Target id is: ", target.targetId);
  } catch (err) {
    console.log(err.response);
  } finally {
    client.close();
  }
}

testCreateBrowserContext().catch((err) => console.error(err));

What is the expected behavior?
Should print a target id, like:

New Target id is:  60AE381193D9FC1EAA55D3100E54F291

What went wrong?
It prints:
{code: -32000, message: "Not allowed."}

Issue is in 'createBrowserContext' call.

Did this work before? Yes Chrome 70

Chrome version: 71.0.3578.98  Channel: stable
OS Version: OS X 10.14.2
Flash Version: 

It stopped working in Chrome 71,  and still doesn't work in nightly Chromium 73 build.