Closed
Bug 1956945
Opened 4 months ago
Closed 2 months ago
"webExtension.uninstall" with an emtpy string as id shouldn't raise an "unknown error"
Categories
(Remote Protocol :: Agent, defect, P3)
Remote Protocol
Agent
Tracking
(firefox140 fixed)
RESOLVED
FIXED
140 Branch
Tracking | Status | |
---|---|---|
firefox140 | --- | fixed |
People
(Reporter: whimboo, Assigned: benchatt)
References
Details
(Whiteboard: [webdriver:m16][webdriver:external][webdriver:relnote][wptsync upstream])
Attachments
(1 file)
Currently our webExtension.uninstall
command returns a unknown failure
when trying to uninstall a web extension with a value of an empty string. Instead we should return a no such webextension
error:
0:19.28 pid:21790 1743110409213 RemoteAgent DEBUG WebDriverBiDiConnection 5f507b0f-ad68-4a19-8fda-aef8ff0ce771 -> {"id":7,"method":"webExtension.uninstall","params":{"extension":""}}
0:19.28 pid:21790 1743110409213 RemoteAgent TRACE Received command webExtension.uninstall for destination ROOT
0:19.28 pid:21790 1743110409213 RemoteAgent DEBUG WebDriverBiDiConnection 5f507b0f-ad68-4a19-8fda-aef8ff0ce771 <- {"type":"error","id":7,"error":"unknown error","message":"[Exception... \"aID must be a non-empty string\" nsresult: \"0x80070057 (NS_ERROR_ILLEGAL_VALUE)\" location: \"JS frame :: resource://gre/modules/AddonManager.sys.mjs :: getAddonByID :: line 2869\" data: no]","stacktrace":"getAddonByID@resource://gre/modules/AddonManager.sys.mjs:2869:24\ngetAddonByID@resource://gre/modules/AddonManager.sys.mjs:4306:33\nuninstall@chrome://remote/content/shared/Addon.sys.mjs:185:45\nuninstall@chrome://remote/content/webdriver-bidi/modules/root/webExtension.sys.mjs:171:22\nhandleCommand@chrome://remote/content/shared/messagehandler/MessageHandler.sys.mjs:260:33\nexecute@chrome://remote/content/shared/webdriver/Session.sys.mjs:390:32\nonPacket@chrome://remote/content/webdriver-bidi/WebDriverBiDiConnection.sys.mjs:236:37\nonMessage@chrome://remote/content/server/WebSocketTransport.sys.mjs:127:18\nhandleEvent@chrome://remote/content/server/WebSocketTransport.sys.mjs:109:14\n"}
This happens because we pass the id of the webextension directly through to the AddonManager which then fails. We probably have to special-case it and check if it's empty first.
Better would be to maybe enforce that in the CDDL but it looks like that empty strings are not supported for the JSON variant.
When we fix that some wdspec tests have to be updated as well.
Reporter | ||
Updated•3 months ago
|
Mentor: hskupin
Severity: -- → S3
Priority: -- → P3
Whiteboard: [webdriver:backlog][lang=js]
Reporter | ||
Comment 1•3 months ago
|
||
There is also the following metadata file that needs an update or as of this state getting removed given that the test will then pass with the requested changes.
Assignee | ||
Comment 2•3 months ago
|
||
Updated•3 months ago
|
Assignee: nobody → bchatterton
Status: NEW → ASSIGNED
Updated•2 months ago
|
Attachment #9479911 -
Attachment description: Bug 1956945 - [webdriver] Check extension not blank r=whimboo! → Bug 1956945 - [webdriver-bidi] Improve "webExtension.uninstall" command for empty extension id r=whimboo!
Pushed by hskupin@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/7e13967666b5
[webdriver-bidi] Improve "webExtension.uninstall" command for empty extension id r=whimboo,webdriver-reviewers
Status: ASSIGNED → RESOLVED
Closed: 2 months ago
status-firefox140:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 140 Branch
Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/52301 for changes under testing/web-platform/tests
Whiteboard: [webdriver:backlog][lang=js] → [webdriver:backlog][lang=js], [wptsync upstream]
Upstream PR merged by moz-wptsync-bot
Reporter | ||
Updated•2 months ago
|
Mentor: hskupin
Whiteboard: [webdriver:backlog][lang=js], [wptsync upstream] → [webdriver:m16][webdriver:external][wptsync upstream]
Reporter | ||
Updated•25 days ago
|
Whiteboard: [webdriver:m16][webdriver:external][wptsync upstream] → [webdriver:m16][webdriver:external][webdriver:relnote][wptsync upstream]
You need to log in
before you can comment on or make changes to this bug.
Description
•