Implement `session.new` command about chromium-bidi HOT 7 OPEN

This is blocking #110: the Firefox implementation strictly follows the spec, and requires a session to be created before accepting any non-static commands.

from chromium-bidi.

Also likely blocking #121.

from chromium-bidi.

As the session should be implemented by the embedder, our NodeJS server simply accepts all the session commands:

from chromium-bidi.

We need this for Puppeteer. Firefox impl supports it and it's part of the spec.

from chromium-bidi.

The best the mapper can do is to send a error "500 | session not created", as the session is already exists at the point mapper is created. And the transport implementation (bidiServerRunner) should implement the proper request handling.

from chromium-bidi.

Closing, as session handling cannot be handled by the Mapper.

from chromium-bidi.

Re-opening this based on the latest understanding that mapper should support multiple sessions and that it should provide handling for capabilities implementable via CDP such as ignoreHTTPSErrors. This capability requires calling Security.setIgnoreCertificateErrors on every target as there is no other way to implement it in Chrome.

from chromium-bidi.