Created attachment 455966 [details]
Patch

Comment on attachment 455966 [details]
Patch

View in context: https://bugs.webkit.org/attachment.cgi?id=455966&action=review

r=me

> Source/WebCore/editing/Editor.cpp:4233
> +        auto& [contentType, preferredFileName, data] = *attachmentInfo;
> +        client->registerAttachmentIdentifier(identifier, contentType, preferredFileName, WTFMove(data));

NIT: Should these all also be `WTFMove` since that's what's done in the IIFE above?

> Tools/TestWebKitAPI/Tests/WebKitCocoa/WKAttachmentTests.mm:1736
> +    NSString *asyncScript = @"return await new Promise(resolve => {"

NIT: Is the `await` actually needed?

(In reply to Devin Rousso from comment #2)
> Comment on attachment 455966 [details]
> Patch
> 
> View in context:
> https://bugs.webkit.org/attachment.cgi?id=455966&action=review
> 
> r=me
> 
> > Source/WebCore/editing/Editor.cpp:4233
> > +        auto& [contentType, preferredFileName, data] = *attachmentInfo;
> > +        client->registerAttachmentIdentifier(identifier, contentType, preferredFileName, WTFMove(data));
> 
> NIT: Should these all also be `WTFMove` since that's what's done in the IIFE
> above?

I'm not sure. `registerAttachmentIdentifier` takes `const String&` anyways, so I just destructured `attachmentInfo` by reference and passed the results to `registerAttachmentIdentifier`. I guess there's no harm in using WTFMove here.

> 
> > Tools/TestWebKitAPI/Tests/WebKitCocoa/WKAttachmentTests.mm:1736
> > +    NSString *asyncScript = @"return await new Promise(resolve => {"
> 
> NIT: Is the `await` actually needed?

Good point. It looks like `-callAsyncJavaScript:` automatically awaits in the case where the script returns a Promise.

Created attachment 455972 [details]
For EWS

Committed r292032 (248975@main): <https://commits.webkit.org/248975@main>

All reviewed patches have been landed. Closing bug and clearing flags on attachment 455972 [details].