summaryrefslogtreecommitdiffstats
path: root/apps/files
Commit message (Collapse)AuthorAgeFilesLines
* [tx-robot] updated from transifexNextcloud bot2018-09-174-2/+10
|
* [tx-robot] updated from transifexNextcloud bot2018-09-162-30/+50
|
* [tx-robot] updated from transifexNextcloud bot2018-09-152-34/+50
|
* [tx-robot] updated from transifexNextcloud bot2018-09-142-0/+4
|
* [tx-robot] updated from transifexNextcloud bot2018-09-134-34/+36
|
* [tx-robot] updated from transifexNextcloud bot2018-09-104-4/+20
|
* [tx-robot] updated from transifexNextcloud bot2018-09-082-20/+20
|
* [tx-robot] updated from transifexNextcloud bot2018-09-042-2/+2
|
* [tx-robot] updated from transifexNextcloud bot2018-09-032-0/+8
|
* [tx-robot] updated from transifexNextcloud bot2018-09-012-0/+2
|
* [tx-robot] updated from transifexNextcloud bot2018-08-314-2/+40
|
* [tx-robot] updated from transifexNextcloud bot2018-08-304-0/+4
|
* [tx-robot] updated from transifexNextcloud bot2018-08-292-0/+2
|
* [tx-robot] updated from transifexNextcloud bot2018-08-274-4/+6
|
* [tx-robot] updated from transifexNextcloud bot2018-08-2410-0/+10
|
* [tx-robot] updated from transifexNextcloud bot2018-08-2340-38/+2
|
* Merge pull request #10565 from ↵Morris Jobke2018-08-201-1/+2
|\ | | | | | | | | nextcloud/stable13-10348-fix-transfering-ownership-of-a-share-to-user-with-same-id-as-receiver [stable13] Fix transfering ownership of a share to user with same id as receiver
| * Fix transfering ownership of a share to user with same id as receiverDaniel Calviño Sánchez2018-08-071-1/+2
| | | | | | | | | | | | | | | | | | When the ownership of a user share is transfered to the receiver the share is removed, as the receiver now owns the original file. However, due to a missing condition, any share with a group, link or remote with the same id as the user was removed, not only the user shares. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
* | [tx-robot] updated from transifexNextcloud bot2018-08-162-64/+64
| |
* | [tx-robot] updated from transifexNextcloud bot2018-08-134-4/+18
| |
* | [tx-robot] updated from transifexNextcloud bot2018-08-082-0/+4
|/
* [tx-robot] updated from transifexNextcloud bot2018-08-022-0/+2
|
* [tx-robot] updated from transifexNextcloud bot2018-07-312-0/+6
|
* [tx-robot] updated from transifexNextcloud bot2018-07-284-0/+8
|
* [tx-robot] updated from transifexNextcloud bot2018-07-274-0/+10
|
* [tx-robot] updated from transifexNextcloud bot2018-07-2612-0/+24
|
* [tx-robot] updated from transifexNextcloud bot2018-07-25122-486/+486
|
* [tx-robot] updated from transifexNextcloud bot2018-07-18128-630/+614
|
* [tx-robot] updated from transifexNextcloud bot2018-07-112-0/+2
|
* [tx-robot] updated from transifexNextcloud bot2018-07-1020-10/+28
|
* [tx-robot] updated from transifexNextcloud bot2018-06-272-2/+50
|
* [tx-robot] updated from transifexNextcloud bot2018-06-272-46/+56
|
* [tx-robot] updated from transifexNextcloud bot2018-06-256-0/+8
|
* [tx-robot] updated from transifexNextcloud bot2018-06-212-0/+2
|
* [tx-robot] updated from transifexNextcloud bot2018-06-19128-364/+396
|
* [tx-robot] updated from transifexNextcloud bot2018-06-174-10/+12
|
* [tx-robot] updated from transifexNextcloud bot2018-06-162-6/+6
|
* [tx-robot] updated from transifexNextcloud bot2018-06-156-10/+14
|
* [tx-robot] updated from transifexNextcloud bot2018-06-142-0/+2
|
* Merge pull request #9837 from ↵Roeland Jago Douma2018-06-132-16/+36
|\ | | | | | | | | nextcloud/stable13-9807-fix-highlighting-of-the-upload-drop-zone [stable13] Fix highlighting of the upload drop zone
| * Do not show an error message when draging and dropping textDaniel Calviño Sánchez2018-06-121-0/+10
| | | | | | | | | | | | | | | | | | | | | | When the browser reports a drag of items other than files (for example, text) and then triggers a drop event with no files no error message should be shown to the user, as in that case there would be no highlight of the drop zone and no indication that the drop would be valid (except for the mouse cursor); the error message should be shown only when the drop event with no files follows a file drag. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
| * Remove no longer needed special handling for FirefoxDaniel Calviño Sánchez2018-06-121-15/+8
| | | | | | | | | | | | | | | | | | | | The highlighting was removed in Firefox when the cursor was no longer moving to handle the behaviour of reporting a file drag and then providing no files in the drop event. That behaviour (which was only present in Firefox 48 and 49) is already handled with the "dropnofiles" callback, so that special handling is no longer needed. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
| * Use "dropnofiles" callback to disable the drop state in the UIDaniel Calviño Sánchez2018-06-121-0/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When a file is dragged from the desktop to the file list the file list is highlighted, and when the file is finally dropped or the drag operation is cancelled the highlighting is removed. In some cases, due to a wrong implementation, a browser may end a file drag with a drop with no files (for example, when a folder or text is dragged), which would cause the highlight to not be removed. Now those cases are handled with the "dropnofiles" callback, which restores the UI and also shows a message to the user. The error message is just a generic one, as in some cases it is not even possible to know whether the problem came from a text drag or a folder drag, and whether the problem appears or not depends on the browser, version and even operating system. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
| * Add callback to clean up after misbehaved drag and drop eventsDaniel Calviño Sánchez2018-06-121-0/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The jQuery Plugin triggers the "dragover" callback when the browser triggers the "dragover" event and the types in their DataTransfer include a "Files" item. It also triggers the "drop" callback when the browser triggers the "drop" event and the list of files in its DataTransfer is not empty. Unfortunately some browsers may trigger "dragover" events with a DataTransfer that includes a "Files" item and then trigger a "drop" event with an empty list of files. When that happens the actions performed in the "dragXXX" callbacks could be left hanging if they were expected to be finished in the "drop" callback (for example, if the drop zone was highlighted during the drag to be then restored when the file was finally dropped). This commit adds the "dropnofiles" callback to be able to handle those situations. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
| * Remove duplicated codeDaniel Calviño Sánchez2018-06-121-6/+1
| | | | | | | | | | | | | | "disableDropState" was set as the event handler in 8d4e5747f386a0, but the duplicated code was accidentally added back in 786e858d23c4a4. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
* | [tx-robot] updated from transifexNextcloud bot2018-06-138-2/+8
|/
* [tx-robot] updated from transifexNextcloud bot2018-06-122-0/+2
|
* [tx-robot] updated from transifexNextcloud bot2018-06-092-0/+2
|
* [tx-robot] updated from transifexNextcloud bot2018-06-084-2/+46
|
* [tx-robot] updated from transifexNextcloud bot2018-06-072-2/+6
|