Uploading files via Drag and Drop doesn't work
- Edited
Version 0.99.120.1-beta (WebKit 614.1.20)
MacBook Pro (macOS Monterey 12.6 build 21G115)
This is similar to a recently fixed issue. Drag and drop from the local file system to trigger an upload is fixed in slack per that issue, but in github.com's pull request compose boxes, Drag and Drop still takes over the entire tab rather than trigger the correct site specific drag and drop handling.
This can be reproduced with any github PR compose input box.
Steps to reproduce:
<Include steps to reproduce the bug; Did you try using Compatibility mode? If applicable, does Safari behave in the same way?>
Expected behavior:
<What you expected to happen?>
Orion, OS version; hardware type:
Image/Video:
<Copy/paste or drag and drop to upload images or videos (up to 20MB)>
Steps to reproduce:
Unable to drag/drop files to the GitHub uploader. It gives warning about directories.
Expected behavior:
Can drag/drop directories to GitHub uploader
Orion, OS version; hardware type:
Latest macOS beta
steps to reproduce: copy a file and paste it into skype or discord (only two that i've tested)
expected behavior: for the file to attach. instead I have to upload the file which means I can't use my standard screenshot copy to clipboard technique, I have to save the screenshot.
M1 Max, 12.6, Version 0.99.120.1-beta (WebKit 614.1.20)
Steps to reproduce:
Start writing a reply to a GitHub issue. Drag and drop a PNG image into the reply.
Instead, Orion opens a link to the local file and replaces the GitHub page (in my case file:///Users/nicholas/Pictures/Screenshots/example.png
).
You can hit the back button and go back to the Github page, but the screenshot still isn't updated
Expected behavior:
Github issue should upload and be inserted into the comment.
Firefox and Safari both work correctly here.
Orion, OS version; hardware type:
Version 0.99.120.1-beta (WebKit 614.1.20)
MacBook Pro (macOS Monterey 12.6 build 21G115)
Image/Video:
- Edited
Besides the issue being annoying (and is fixed in next release) it also has the record 8 merges, meaning 8 different people created the bug report for the same issue, without this popping out in automatic search.