Open
Bug 1830897
Opened 2 years ago
Updated 1 year ago
Enable async stack traces on the default realm as early as possible
Categories
(Remote Protocol :: WebDriver BiDi, defect, P3)
Remote Protocol
WebDriver BiDi
Tracking
(Not tracked)
NEW
People
(Reporter: jdescottes, Unassigned)
References
(Depends on 1 open bug, Blocks 1 open bug)
Details
(Whiteboard: [webdriver:backlog])
In Bug 1788894, we had to delay the enabling of async stack traces until the first usage of of a script evaluation API, because otherwise we had a race condition between the MessageHandler's destroy and constructor.
See the detailed explanations at Bug 1788894 comment 7 and below.
However, enabling async stacktraces early is mandatory in order to support those for log entryAdded events. Otherwise with the current implementation it would depend on having a first call to a script evaluation API.
|
Reporter | |
Updated•2 years ago
|
Points: --- → 2
Priority: -- → P3
Whiteboard: [webdriver:backlog]
|
|
Reporter | |
Updated•2 years ago
|
Severity: -- → S3
|
|
Reporter | |
Comment 1•1 year ago
|
||
See last comments in Bug 1788894, we should handle unsetting async stacktraces via native code. If we no longer disable this via JS then we can enable them as early as possible
You need to log in
before you can comment on or make changes to this bug.
Description
•