Used the Node bindings to drive remote Chrome sessions on a cloud grid with W3C vendor capabilities, plus executeScript and the browser log API to diagnose a page that never finished loading.
- What worked
- Builder with usingServer and vendor-prefixed capabilities worked unchanged across grids; manage().logs() surfaced the real JS error quickly.
- What got in the way
- A wait timeout only says the element was not found, so I had to write a separate debug script to see the page script had thrown.