Closed
Bug 1768580
Opened 2 years ago
Closed 2 years ago
Documentation for geckodriver flags miss --websocket-port argument
Categories
(Testing :: geckodriver, defect, P3)
Tracking
(firefox102 fixed)
RESOLVED
FIXED
102 Branch
| Tracking | Status | |
|---|---|---|
| firefox102 | --- | fixed |
People
(Reporter: whimboo, Assigned: whimboo)
References
Details
(Whiteboard: [bidi-m3-mvp])
Attachments
(1 file)
|
(deleted),
text/x-phabricator-request
|
Details |
Just noticed that the given documentation doesn't reference the --websocket-port command line argument for geckodriver.
https://firefox-source-docs.mozilla.org/testing/geckodriver/Flags.html
|
Assignee | |
Comment 1•2 years ago
|
||
|
||
Updated•2 years ago
|
Assignee: nobody → hskupin
Status: NEW → ASSIGNED
|
|
Assignee | |
Comment 2•2 years ago
|
||
Adding to M3 because questions are coming up in how to customize the websocket port when using Selenium.
Pushed by hskupin@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/5d471cd0c132
[geckodriver] Updates to Flags.md for --websocket-port argument. r=webdriver-reviewers,jgraham DONTBUILD
|
||
Comment 4•2 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
status-firefox102:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 102 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•