See https://fs.spec.whatwg.org/#filesystemhandle, we don't seem to be doing step 1: > Their deserialization steps, given serialized and value are: > > 1. If serialized.[[Origin]] is not same origin with value’s relevant settings object's origin, then throw a DataCloneError. > > 2. Set value’s entry to serialized.[[Entry]] Attaching a mochitest, but there do seem to be WPTs that test this already (right now all testing/web-platform/tests/fs WPTs fail for me, even with `dom.fs.enabled` set to `true`). I often try to annotate code with the steps from the spec algorithm (within reason), to make sure I don't forget any.
Bug 1790207 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
See https://fs.spec.whatwg.org/#filesystemhandle, we don't seem to be doing step 1: > Their deserialization steps, given serialized and value are: > > 1. If serialized.[[Origin]] is not same origin with value’s relevant settings object's origin, then throw a DataCloneError. > > 2. Set value’s entry to serialized.[[Entry]] Attaching a mochitest, but there do seem to be WPTs that test this already (though right now all testing/web-platform/tests/fs WPTs fail for me, even with `dom.fs.enabled` set to `true`). I often try to annotate code with the steps from the spec algorithm (within reason), to make sure I don't forget any.