Provide support for various tabs and windows. This can be exercised by identifying frameId values returned by CDP and pushing those values into an array. The interface that defines tests testBrowserItem would need to be extended to account for a new property accounting for window as a number type.

At this time it is mandatory to specify ports when testing against Firefox based browsers. I would like port specification to be optional.

For ports to be optional I need to be able to supply a port value of 0 to Firefox when running the flag -start-debugging-server. Firefox does accept a 0 value, which provides a service on a randomly available TCP port. Unfortunately nobody knows how to make Firefox indicate what that port number is.

https://github.com/prettydiff/drial/blob/master/documentation/problems.md#firefox

https://bugzilla.mozilla.org/show_bug.cgi?id=1721371

https://bugs.chromium.org/p/chromium/issues/detail?id=1231082

Clicking on a hyperlink with an attribute target="_blank" normally produces a new tab with the page content of the requested hyperlink location.

When doing this via remotely via test execution CDP reports a Page.windowOpen event and a HTTP request to /json/list reports a new page. In the actual chrome (shell) of the browser there is no new tab. Performing the event multiple times repeats the same behavior.

Launching chrome for remote debugging --remote-debugging-port and with devtools on --auto-open-devtools-for-tabs breaks Chrome's ability to redirect traffic to domains via CDP.

I opened a defect with the Chromium team: https://bugs.chromium.org/p/chromium/issues/detail?id=1230398

https://github.com/prettydiff/drial/blob/master/documentation/problems.md#chrome

If Firefox ever caches the localhost domain against the https scheme the browser is effectively killed for testing. This is because executing Firefox with flag start-debugging-server will create a localhost service on the specified port, but that service only listens on http and insecure websockets. If Firefox caches the localhost domain against the https scheme then every request to localhost will be upgraded to https dynamically and so there is no means to access services from the browser.

Uninstalling the browser and reinstalling it is not enough. Uninstalling the browser will not remove cached browser assets and reinstalling the browser will automatically recognize and incorporate those cached assets.

https://github.com/prettydiff/drial/blob/master/documentation/problems.md#firefox

https://bugzilla.mozilla.org/show_bug.cgi?id=1679249

https://bugzilla.mozilla.org/show_bug.cgi?id=1601695

This application will not work with Firefox until Firefox adds support for this necessary CDP feature.

https://chromedevtools.github.io/devtools-protocol/tot/Page/#method-addScriptToEvaluateOnNewDocument

Allow history navigation is a test interaction event. This is effectively allowing the user to click the back button or forward button of the browser, but this interaction can occur directly in the page using JavaScript and the history API. I just need to update the testBrowserItem interface to allow these new events.

Should be as simple as new event names: historyBack and historyForward.