chrominator
chrominator copied to clipboard
jesg
high level api to the chrome remote debugger
if navigation is triggered then chromedriver should wait for navigation to complete in the following scenarios: * user clicks on a node * user sends keys to a node it...
this should set the size of the current window. the chrome remote debugger 1.2 api and the tip of the tree api are not compatible.
we should roughly follow the webdriver api. we don't need to handle content editable or resettable elements in the first implementation. https://www.w3.org/TR/webdriver/#element-clear
this should return the visible text via `element.innerText`. this will probably not be compatible with webdriver which cleans some of the whitespace.
we should be able to listen to network requests with the [Network](https://chromedevtools.github.io/devtools-protocol/tot/Network/) api.
we should be able to use the [CacheStorage](https://chromedevtools.github.io/devtools-protocol/tot/CacheStorage/) api to do this.
the user should be able to switch between windows. docs: https://chromedevtools.github.io/devtools-protocol/tot/Browser/
we need to research the [target](https://chromedevtools.github.io/devtools-protocol/tot/Target/) api. we need to test behavior around BrowserContext. it would be really cool if we could isolate cookies, local storage etc. with this feature.