[Bug]: Errors reported from validation_errors.cc and interface_endpoint_client.cc when dragging something out of Electron

[sschultze]

Preflight Checklist

• I have read the Contributing Guidelines for this project.
• I agree to follow the Code of Conduct that this project adheres to.
• I have searched the issue tracker for a bug report that matches the one I want to file, without success.

Electron Version

28.2.2

What operating system are you using?

macOS

Operating System Version

macOS Sonoma 14.2.1

What arch are you using?

arm64 (including Apple Silicon)

Last Known Working Electron version

No response

Expected Behavior

Create a draggable element:

<div id="myDraggable" draggable="true" style="width: 32px; height: 32px; background-color: Red;" />

Attach an event handler for the dragstart event:

window.addEventListener('DOMContentLoaded', () => {
    document.getElementById('myDraggable').addEventListener('dragstart', (event) => {
        event.dataTransfer.setData('text/plain', 'Hello world.');
    });
})

Start the application and drag the red box somewhere, e.g. into Finder, into Visual Studio Code, or into TextEdit.

This works fine, but I expect that no internal errors are logged.

Actual Behavior

Electron or Chromium internal errors are logged. You can see them in the Fiddler console too, but also in the "normal" console when starting the Electron app from Terminal.

[8806:0210/102743.874133:ERROR:validation_errors.cc(117)] Invalid message: VALIDATION_ERROR_UNKNOWN_ENUM_VALUE
[8806:0210/102743.874179:ERROR:interface_endpoint_client.cc(702)] Message 549403661 rejected by interface blink.mojom.FrameWidget

The message number (here: 549403661) differs when a different Electron version is used. Also, in 29.0.0-beta.8, the line number in interface_endpoint_client.cc is different (707 instead of 702).

From the user perspective however, everything works fine.

Testcase Gist URL

https://gist.github.com/sschultze/e569bb2187cda685e61079b86df22e81 (added)

Additional Information

My application does not actually allow to drag text/plain, I have chosen this only for simplicity of reproduction. The errors seem to be logged for any data transfer object regardless of its contents.

I have tried 29.0.0-beta.8 too, same issue.

[sschultze]

On my Windows 11 machine, the errors are not logged.

[electron-issue-triage]

Hello @sschultze. Thanks for reporting this and helping to make Electron better!

Would it be possible for you to make a standalone testcase with only the code necessary to reproduce the issue? For example, Electron Fiddle is a great tool for making small test cases and makes it easy to publish your test case to a gist that Electron maintainers can use.

Stand-alone test cases make fixing issues go more smoothly: it ensure everyone's looking at the same issue, it removes all unnecessary variables from the equation, and it can also provide the basis for automated regression tests.

Now adding the blocked/need-repro Needs a test case to reproduce the bug label for this reason. After you make a test case, please link to it in a followup comment. This issue will be closed in 10 days if the above is not addressed.

[sschultze]

This is the gist for Electron Fiddle:

https://gist.github.com/sschultze/e569bb2187cda685e61079b86df22e81

Keep in mind that the errors are logged on macOS (I've tried arm64).

[electron-issue-triage]

This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment (for example, "bump"), and we'll keep it open. If you have any new additional information—in particular, if this is still reproducible in the latest version of Electron or in the beta—please include it with your comment!

[sschultze]

bump