Add support of synthetic navigation to HTTP driver

[ziflex]

Right now, pages created by in-memory http driver does not support navigation between pages due to their static nature.
It makes it problematic to "move" from one static page to another within a same domain simply because we cannot reuse current page. In order to do so, we have to create a new page every time we need to move from A to B.
Let's add a possibility to reuse existing page by implementing synthetic navigation that would just download a new HTML page by a given URL and replace root element.

[slowmanchan]

Would love to help out here but I'm not too sure whats required here. Could you please elaborate a bit more? Thanks!

[ziflex]

Great!
So, we have a main Page interface as an abstraction and 2 implementations aka drivers:

• Chrome Devtools Protocol based aka CDP
• In-memory based aka HTTP

CDP driver is a "remote control" to your browser where all pages are loaded and interactions occur.
But HTTP driver just loads HTML pages into memory and parses them, hence no user interactions like clicking and selecting can happen. But, some of the interactions can be emulated and one of the interactions is navigation between pages.
With CDP driver, you can just write NAVIGATE(page, newUrl) and it will navigate the current page/browser tab to a new location. HTTP driver does not do it but it does not mean it cannot. We can simply load a new page and flush the previous one. That's basically what this issue is about.

You can see here that the method exists but is not implemented. (the ignored argument is a target URL).

[slowmanchan]

Thanks for the info.
I'll check it out!

[slowmanchan]

I've got a WIP PR. It works but is this what you mean? Also, can you let me know what your development process is? I'm currently compiling after code changes and testing manually with an .fql file. I'd also like to cover this with some tests but i'm not sure how to go about it (mocking drivers / objects).