Bug 192605 - Make CloneDeserializer succeed deserialization for DOM objects in non JSDOMGlobalObject context
Summary: Make CloneDeserializer succeed deserialization for DOM objects in non JSDOMGl...
Status: RESOLVED DUPLICATE of bug 192606
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebCore Misc. (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-12-11 14:07 PST by youenn fablet
Modified: 2018-12-11 23:51 PST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description youenn fablet 2018-12-11 14:07:01 PST 
Deserialization is used in non JSDOMGlobalObject context for IDB in NetworkProcess to get access to the value in case of key path use.
Currently, deserialization fails as DOM objects require a JDOMGlobalObject.

In the context of IDB, there is no need for the exact JS wrapper.
An empty object might be sufficient if the key path is not a property or sub property of the JS DOM object.
Comment 1 Alexey Proskuryakov 2018-12-11 23:51:03 PST 

*** This bug has been marked as a duplicate of bug 192606 ***