Closed
Bug 1969880
Opened 1 year ago
Closed 14 days ago
Clean up user context state when it's removed without WebDriver BiDi
Categories
(Remote Protocol :: WebDriver BiDi, task, P3)
Remote Protocol
WebDriver BiDi
Tracking
(firefox156 fixed)
RESOLVED
FIXED
156 Branch
| Tracking | Status | |
|---|---|---|
| firefox156 | --- | fixed |
People
(Reporter: Sasha, Assigned: sameembaba, Mentored)
References
(Blocks 1 open bug)
Details
(Whiteboard: [webdriver:m21][webdriver:external][lang=js])
Attachments
(1 file)
With bug 1967653 and bug 1967653 we added the state when a user context is created. We clean up this state when "browser.removeUserContext" command is called, but if a user context is deleted outside of WebDriver BiDi we miss clearing it until the session is deleted. It shouldn't cause any direct issue, but still would nice to clean it up. For this, we probably could let the UserContextManager emit events when a user context is destroyed, and then the browser modules could run the cleanup steps.
| Reporter | ||
Updated•1 year ago
|
Priority: -- → P3
Whiteboard: [webdriver:backlog]
| Reporter | ||
Updated•1 year ago
|
Mentor: aborovova
Whiteboard: [webdriver:backlog] → [webdriver:backlog][lang=js]
| Reporter | ||
Updated•1 month ago
|
Assignee: nobody → ssssameembaba
Status: NEW → ASSIGNED
| Assignee | ||
Comment 1•23 days ago
|
||
Pushed by aborovova@mozilla.com:
https://github.com/mozilla-firefox/firefox/commit/e16135114651
https://hg.mozilla.org/integration/autoland/rev/27c805352a6c
Clean up WebDriver BiDi user context state when deleted externally. r=Sasha
Comment 3•14 days ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 14 days ago
status-firefox156:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 156 Branch
Comment 4•13 days ago
|
||
Sameem, would bug 1958852 be a good candidate you might be interested in? It would be good to see those two sync modules merged.
Flags: needinfo?(ssssameembaba)
Whiteboard: [webdriver:backlog][lang=js] → [webdriver:m21][webdriver:external][lang=js]
You need to log in
before you can comment on or make changes to this bug.
Description
•