Open
Bug 1985991
Opened 9 months ago
Updated 8 months ago
"script.realmDestroyed" is inappropriately emitted after the "browsingContext.contextDestroyed" event
Categories
(Remote Protocol :: WebDriver BiDi, defect, P2)
Remote Protocol
WebDriver BiDi
Tracking
(Not tracked)
NEW
People
(Reporter: whimboo, Unassigned)
References
(Blocks 2 open bugs)
Details
(Whiteboard: [webdriver:backlog])
When a browsing context is destroyed and it contains custom realms (sandboxes) created via WebDriver BiDi, the associated script.realmDestroyed events are currently emitted after the browsingContext.contextDestroyed event. This delay may lead to issues for clients that assume realms are torn down before the browsing context itself.
To avoid such inconsistencies, we should ensure that when a browsing context is scheduled for destruction, all realms within that context are immediately finalized, triggering their corresponding script.realmDestroyed events before emitting browsingContext.contextDestroyed.
|
Reporter | |
Updated•8 months ago
|
Priority: -- → P2
Whiteboard: [webdriver:backlog]
|
||
Updated•8 months ago
|
Points: --- → 3
|
||
Comment 1•8 months ago
|
||
The severity field is not set for this bug.
:whimboo, could you have a look please?
For more information, please visit BugBot documentation.
Flags: needinfo?(hskupin)
|
|
Reporter | |
Updated•8 months ago
|
Severity: -- → S3
Flags: needinfo?(hskupin)
You need to log in
before you can comment on or make changes to this bug.
Description
•