Opera
| Image | websummoner/opera |
| Browser | Opera 135.0.5973.76 (Chromium 151) |
| Driver | OperaDriver 151.0.7922.176 |
How it works
Section titled “How it works”Opera is the awkward one, for two reasons.
Driver tags follow Chromium, not Opera. operachromiumdriver releases are
numbered by the Chromium version Opera is built on — Opera N ships Chromium
N+16. Passing -d 135.0.… fetches a driver sixteen majors too old, which
refuses every session. The tool works out the Chromium line itself, so do not
pass -d.
Opera publishes late. A new Opera often ships before the driver for its
Chromium line exists, so the tool falls back to the newest operadriver — never
a chromedriver. The version check in this family is a warning, not a refusal,
so a driver one line behind still drives the browser and logs
This version of OperaDriver has not been tested with Opera version 151.Substituting a Chrome for Testing chromedriver also starts sessions, but crashes the renderer whenever a page opens a window: Opera patches its Chromium and only its own driver accounts for that. A real driver one line behind beats a foreign driver on the exact line.
The current image needs no fallback — OperaDriver 151.0.7922.176 matches the Chromium line Opera 135 is built from.
Two more behaviours show through to tests, documented on the hub’s Opera section: operadriver answers in legacy JSONWP unless asked for W3C (the hub asks), and a fresh session reports Opera’s own UI pages as extra window handles.
Building
Section titled “Building”./images opera -b 135.0.5973.76 -t websummoner/opera:135.0