DragPromisedFileTo path-collision POC (macOS)

Setup: create a file named Resume.pdf in the folder you will drop into (e.g. ~/Desktop/droptest/Resume.pdf) so that a collision occurs.

Drag me to a Finder folder
that already contains Resume.pdf

Expected (buggy) result: Chrome creates Resume-1.pdf in the drop directory containing the bytes downloaded from this server, but returns the path to the pre-existing Resume.pdf as the fulfilled file-promise URL. The drop target (Finder selection, Mail attachment, Slack upload, etc.) therefore acts on the user's pre-existing local file instead of the downloaded content.