[Webkit-unassigned] [Bug 220038] Unable to postMessage a WebAssembly module to a worklet

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=220038

--- Comment #9 from Chris Dumez <cdumez at apple.com> ---
(In reply to Chris Dumez from comment #8)
> (In reply to Chris Dumez from comment #7)
> > (In reply to Richard Newman from comment #6)
> > > I have not tested iframe messaging.
> > > 
> > > Web worker to page seems to work correctly.
> > 
> > Oh I see. If worker to page works then I would imagine iframe messaging
> > would work too. This must be specific to worklets somehow.
> 
> In SerializedScriptValue:
> 
>                 if (m_context != SerializationContext::WorkerPostMessage) {
>                     code = SerializationReturnCode::DataCloneError;
>                     return true;
>                 }
> 
> When encoding wasm modules. We are likely not using the WorkerPostMessage
> SerializationContext when messaging audio worklets?

MessagePort::postMessage() seems to use the default serialization context, no matter in which context the message port is used:

===
ExceptionOr<void> MessagePort::postMessage(JSC::JSGlobalObject& state, JSC::JSValue messageValue, PostMessageOptions&& options)
{
    LOG(MessagePorts, "Attempting to post message to port %s (to be received by port %s)", m_identifier.logString().utf8().data(), m_remoteIdentifier.logString().utf8().data());

    registerLocalActivity();

    Vector<RefPtr<MessagePort>> ports;
    auto messageData = SerializedScriptValue::create(state, messageValue, WTFMove(options.transfer), ports);
===

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20210105/dd9c369c/attachment-0001.htm>