Investigate potential issues with nsIWorkerDebugger.initialize
Categories
(Remote Protocol :: WebDriver BiDi, task, P2)
Tracking
(firefox141 fixed)
| Tracking | Status | |
|---|---|---|
| firefox141 | --- | fixed |
People
(Reporter: jdescottes, Assigned: jdescottes)
References
(Blocks 1 open bug)
Details
(Whiteboard: [webdriver:m16])
Attachments
(1 file, 2 obsolete files)
While prototyping worker support in BiDi, I noticed we rely on nsIWorkerDebugger initialize to load the "startup" script in devtools and this in turn makes the nsIWorkerDebugger instance initialized.
void initialize(in AString url);
readonly attribute boolean isInitialized;
This sounds fine as long as only DevTools is only using the API. But if we consider scenarios where BiDi is monitoring events on workers and we also want to open the DevTools toolbox, both protocols might try to call initialize on the same nsIWorkerDebugger instance. If BiDi already "initialized" the WorkerDebugger, DevTools will not try to load its script and won't be able to interact with the worker.
I can see two options here:
- we extend initialize to make it more flexible
- or both DevTools and BiDi use the same startup script?
Alex: any thoughts here?
| Assignee | ||
Updated•1 year ago
|
Updated•1 year ago
|
| Comment hidden (hide) |
Updated•1 year ago
|
| Comment hidden (hide) |
| Comment hidden (hide) |
| Comment hidden (hide) |
| Comment hidden (hide) |
| Assignee | ||
Updated•1 year ago
|
| Comment hidden (hide) |
| Comment hidden (hide) |
| Assignee | ||
Comment 8•1 year ago
|
||
| Assignee | ||
Comment 10•1 year ago
|
||
We should be able to reuse devtools/server/startup/shared-worker-initializer.js easily for BiDi now. The change was rather small so downgrading to 2P.
Comment 11•1 year ago
|
||
Comment 12•1 year ago
|
||
| bugherder | ||
Description
•