Benches macOS

5

Folder close automatically after moving a…

apple Verified

Imported from the Apple Support Forums via the Wayback Machine 🔗

Hi,

I usually work in column view. When I'm going to move a file to a sub-folder in this column, the finder closes automatically all subfolders after dopping the file. This is very annoying, if you want to work in this subfolder - because you have to open it again after dropping the file.

This is new under 10.5 - until 10.4 the finder has left all subfolders open. Has anyone an idea how to solve this problem?

Thanks

Hagbard

5 replies

Sign in or join Beachball Help to reply.

  1. 0

    Francine Schwieder

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I've noticed the change in behavior too, and it is both counter-intuitive, different that it has been since day one of OS X, and completely goofy. Send feedback to Apple here:

    http://www.apple.com/feedback/macosx.html/

    Personally, I consider it a bug, not a feature. You can move files back UP the hierarchy, but not down. If your Finder view was going to automatically change, logically it should change when you move something back up: one would assume you want to be in the folder you are putting the file in, but that's not the way it is currently working. Maybe some coder had an attack of dyslexia. Very annoying.

    Francine

    User uploaded file

    Francine
    Schwieder

  2. 0

    roam

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Hello

    In Finder Preferences, check to see that you have selected, Spring loaded folders and windows, for I do not experience the problem. Perhaps this is the difference.

  3. 0

    roam

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Ah, I see what you mean, it only works in one direction. So I added to the feedback.

  4. 0

    tracy_lin_chiappari

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Didn't notice this until my roommate commented on how annoying it was. I can't see how it isn't a bug. It makes no sense.

  5. 0

    Werner Kranwetvogel

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    It was obviously a bug in 10.5 and it seems to be fixed in 10.6. Thanks Apple for adressing this, that's very helpful in my daily workflow!