Since the latest update, when deleting a file, the blue selection on file disappears instead of going to the next one. It goes back to the beginning of the folder and I have to select again the file/picture I was arrived at. Not efficient when you have a huge selection. If I choose "refuse", the blue selection stays and it goes to the next file as usual, but it makes me work twice and loose time. I could use only "delete" and the right arrow so it was easy, but I now need the mouse to reselect the file...
I tried to reset everything but the issue remains with delete.
Does anyone know how to fix that?
[Moved from Creative Cloud to Bridge by moderator. || Note: BRIDGE-8932 ]
This is a known bug in the most recent release and the tech team is working on it now. Hopefully they will have a fix soon. You can always go back a version and uninstall this version until they fix the issue.
There has been a longstanding issue with large folders, where a deletion isn't always immediate, or where the entire file list reloads after deleting, or if you have scrolled past the deleted file, Bridge jumps back to the next file once it finally performs the deletion. Just not good folder listing code. Compare it to other file browsers (Finder, Explorer, Faststone Image Viewer, etc.)
Thanks to all!
Was this issue resolved?
Hi. This is not fixed - I am using Bridge 10.0.1.126 on Mojave
The "Deselect in Bridge after deleting a file" has been addressed in v10.0 which will be released early next month.
If you need early access to this release, you can sign up for the prerelease program from https://adobeprerelease.com under NDA.
Select Adobe Bridge. Once we approve your request, you will be able to download v10.0 (choose the latest drop).
Please check this build and report back.
Behavior still exists. However, strangely, it exists on the Macbook Pro but doesn't exist on the iMac. Both Macs are running Catalina, and are up to date on OS updates.
*** Correction ***
I just got into the office and while yesterday I observed that Bridge 2020 in the iMac had seemed to fix this behavior, alas it has not. It seems that during the sleep/wake up function, the Bridge jumping behavior has reemerged. So this behavior still exists, for sure in both environments.
This problem is still occuring in the latest version of Bridge. I just downloaded it today (10.3). Very frustrating. When will this be fixed?
This is not solved. Please take this post off "Solved" please.
any update on this?
As of late, no update or word from Adobe.
This is not solved. I am late to the problem, because i never update my software right away since this has happened in the past. How can we download the previous working version 9.03? And when we install a new version, is there a way to keep the old version from being uninstalled? Before CC I always kept the last couple update installers just in case this sort of thing happened. Now it's not possible..seemingly.
This is not fixed - I am using Bridge 10.0.1.126 on Mojave
It is february 2020 now. I still have this problem. Anyone got it solved?
It is supposedly fixed in the current release, I haven't seen it happen recently myself.
Unfortunately not. On my Macbook with OS 10.15.2 and 10.0.2 the bug is back. 😞
Sorry you're seeing it in the current release, can you verify you're indeed using 10.0.2?
If so, the engineering team would like to work with you to investigate this further;
Can you provide screenrecording of this happening on your system?
Would you be willing and interested in working towards resolution with our engineering team via screenshare?
Of course I using current Bridge version. 🙂
And yes, also I would be interested in a screenshare. How do we meet?
I've asked our engineering team to follow up with you via email regarding the screenshare.
Let us know how it goes!
I concur. It is not fixed on my end either. I just installed the latest release too.
With the help of dominikgeisler, the Bridge engineering team has been able to reproduce this issue and is working towards a fix. Thank you Dominik for the assistance and willingness to help out here. We'll get a fix out as soon as we can.
Cool! When should we expect an update?