Uh oh!
There was an error while loading. Please reload this page.
fix(files): drag and drop - #42366
Conversation
8025f26 to
5d76500CompareSigned-off-by: John Molakvoæ <skjnldsv@protonmail.com>
Signed-off-by: John Molakvoæ <skjnldsv@protonmail.com>
Signed-off-by: John Molakvoæ <skjnldsv@protonmail.com>
5d76500 to
dc82c27Compareskjnldsv
commented
Dec 20, 2023
/backport to stable28 |
The backport to stable28 failed. Please do this backport manually. # Switch to the target branch and update it
git checkout stable28
git pull origin stable28
# Create the new backport branch
git checkout -b fix/foo-stable28
# Cherry pick the change from the commit sha1 of the change against the default branch# This might cause conflicts. Resolve them.
git cherry-pick abc123
# Push the cherry pick commit to the remote repository and open a pull request
git push origin fix/foo-stable28Error: Unknown error More info at https://docs.nextcloud.com/server/latest/developer_manual/getting_started/development_process.html#manual-backport |
skjnldsv
commented
Dec 20, 2023
/backport dbfd8f6 to stable28 |
The backport to stable28 failed. Please do this backport manually. # Switch to the target branch and update it
git checkout stable28
git pull origin stable28
# Create the new backport branch
git checkout -b fix/foo-stable28
# Cherry pick the change from the commit sha1 of the change against the default branch# This might cause conflicts. Resolve them.
git cherry-pick abc123
# Push the cherry pick commit to the remote repository and open a pull request
git push origin fix/foo-stable28Error: Unknown error More info at https://docs.nextcloud.com/server/latest/developer_manual/getting_started/development_process.html#manual-backport |
HLFH
commented
Jan 25, 2024
Fixed on Chrome but not on Safari. No? @skjnldsv |
It is still broken on Safari. #43135 |
It's still broken on V28 and Firefox too. (same installation, same client machine, only the browser is different) |
bfrmtx
commented
Jun 2, 2024
On Arch Linux: |
susnux
commented
Jun 2, 2024
@bfrmtx please open a new issue for this with more information (use the template on issue creation). |
Fix#42252
Fix#42136
Fix#42252