Open
Bug 1832248
Opened 11 months ago
Updated 11 months ago
Consider using or removing structured clone OwnTransferablePolicy::NoTransferables
Categories
(Core :: JavaScript Engine, task, P2)
Core
JavaScript Engine
Tracking
()
NEW
People
(Reporter: sfink, Unassigned)
References
(Blocks 1 open bug)
Details
The current code only checks against OwnsTransferablesIfAny, so NoTransferables and IgnoreTransferablesIfAny are effectively identical.
The intention of NoTransferables was for (1) API usage assertions, and (2) places where it was not yet known which of the other two possibilities it would become (so an initial "not yet known" value). (2) sounds important, yet given the actual usage it appears that it is not (any longer?) needed.
|
||
Updated•11 months ago
|
Severity: -- → N/A
Priority: -- → P2
You need to log in
before you can comment on or make changes to this bug.
Description
•