Bridge doesn't handle relative symlinks correctly

While Adobe Bridge seem to have some understanding of symlinks on macOS, it only seems to handle absolute symlinks right. When it comes to relative symlinks, the Content pane does show the correct thumbnails, but when you try to open them, Bridge appears to resolve the symlinks against the root directory (/) instead of the directory in which they reside.

Here’s an easy way to reproduce this:

1. Create a folder Foo with a folder Bar within it:
   $ mkdir Foo Foo/Bar
   $ cd Foo
2. Create an absolute symlink in Foo pointing to Bar:
   $ ln -s $(pwd)/Bar AbsoluteBar
3. Create a relative symlink in Foo pointing to Bar:
   $ ln -s Bar RelativeBar
4. Create another relative symlink in Foo pointing to Users (which doesn’t exist):
   $ ln -s Users RelativeUsers
5. Open Foo in Bridge.
6. Note: AbsoluteBar and RelativeBar are shown as folders with an arrow superimposed on them while RelativeEtc is shown as a generic document icon with an arrow.
7. Try to open AbsoluteBar by double clicking on it.
8. Note: It opens up and shows an empty Bar folder.
9. Go back and try to open RelativeBar by double clicking on it.
10. Note: Nothing happens.
11. Try to open RelativeUsers by double clicking on it.
12. Note: Bridge resolves the symlink against / instead of Foo and incorrectly shows the content of /Users.

This is bad. Very bad.

While absolute symlinks and aliases can be used as limited workarounds, they are not workable replacements for directory trees that reside on external hard drives and get moved between computers where they get different mount points, or directory trees that are synced between different computers, and aliases in particular don’t work with the shell, nor do they work on other systems than Macs. For this, relative symlinks are required.