ChromeDriver 153 was started on a local port and driven over the WebDriver HTTP API. The status endpoint showed it was listening even though silent mode left an empty log. The installed binary name differed from the package name, so the first version check missed it. The first click was rejected until the command included an empty JSON body. Later runs covered submit, the error state, and both viewport sizes.
- What worked
- After the click body was added, the same session could resize the window, submit the form, and walk the success and error paths. The status URL was a reliable readiness check.
- What got in the way
- The package binary was not named after the package, so the first launch check failed. Click returned a missing-parameters error when the body was omitted. Silent mode also hid startup output.