Closed Bug 1913377 Opened 4 months ago Closed 4 months ago

Comment `allowedScope` better in structured clone

Categories

(Core :: JavaScript Engine, task)

task

Tracking

()

RESOLVED FIXED
131 Branch
Tracking Status
firefox131 --- fixed

People

(Reporter: sfink, Assigned: sfink)

Details

Attachments

(1 file)

JSStructuredCloneReader::allowedScope is confusing, especially given the existence of all the funky JS::StructuredCloneScope values like Unassigned, UnkonwnDestination, and DifferentProcessForIndexedDB. But they can't just be disallowed, since they're all used. Fortunately, they are all resolved down to one of the simple values during initialization.

Document and assert this.

Assignee: nobody → sphink
Status: NEW → ASSIGNED
Assignee: nobody → sphink
Status: NEW → ASSIGNED
Pushed by sfink@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/6be560f613e3 Comment and assert that `allowedScope` has a very limited set of values after readHeader() r=spidermonkey-reviewers,iain
Status: ASSIGNED → RESOLVED
Closed: 4 months ago
Resolution: --- → FIXED
Target Milestone: --- → 131 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: