Add type field to "ScriptEvaluateResult" for "success" or "exception"
Categories
(Remote Protocol :: WebDriver BiDi, task, P1)
Tracking
(firefox110 fixed)
| Tracking | Status | |
|---|---|---|
| firefox110 | --- | fixed |
People
(Reporter: whimboo, Assigned: whimboo)
References
()
Details
(Whiteboard: [webdriver:m5][wptsync upstream][webdriver:relnote])
Attachments
(2 files)
Filed as: https://github.com/w3c/webdriver-bidi/issues/339
Right now the ScriptEvaluateResult could contain a result or an exception. The client can only differentiate between those depending on which field is set. There might be cases when no field or both fields are set.
To make it obvious for the client such a type field should be added to the ScriptEvaluateResult field.
Also the webdriver bidi client needs to be updated to check for that field.
| Assignee | ||
Updated•2 years ago
|
| Assignee | ||
Comment 1•2 years ago
|
||
Updated•2 years ago
|
| Assignee | ||
Comment 2•2 years ago
|
||
Depends on D163830
| Assignee | ||
Comment 3•2 years ago
|
||
Note that we can only land the first patch for now. The webdriver test related changes have to wait until chromedriver has the type field in a release as well.
| Assignee | ||
Comment 5•2 years ago
|
||
Marking bug as leave-open given that we have to wait for the remaining patch to land until both Firefox and Chrome have this field set in release versions. Once that's done I'll land the test change.
Comment 6•2 years ago
|
||
| bugherder | ||
| Assignee | ||
Comment 7•2 years ago
|
||
I discussed with Maksim the landing of the remaining patch and he told me that it will be fine today. So I'm going ahead and land the remaining piece.
Comment 10•2 years ago
|
||
| bugherder | ||
Comment 15•2 years ago
|
||
Comment 16•2 years ago
|
||
| bugherder | ||
| Assignee | ||
Updated•2 years ago
|
Description
•