file-system-access icon indicating copy to clipboard operation
file-system-access copied to clipboard

Handling of symbolic links (symlinks)

Open foolip opened this issue 5 years ago • 4 comments

The spec currently doesn't say anything about how to handle symbolic links. Basic questions:

  • do they appear at all, and then as the type of the thing they point to?
  • are symlink loops exposed to scripts or detected by the UA?

foolip avatar Nov 20 '19 10:11 foolip

@mkruisselbrink any update on this?

ftreesmilo avatar Jul 18 '21 19:07 ftreesmilo

Our current implementation appears to be inconsistent between platforms with how symlinks are treated. I think ideally we'd treat symlinks as the thing they point to without any special treatment. It would then be up to websites to deal with symlink loops etc. If we ever add a "recursive" mode to directory iteration though we'd have to figure out what to do with symlink loops in that case.

Whatever we want to do here, definitely needs to be written down in the spec.

mkruisselbrink avatar Jul 20 '21 20:07 mkruisselbrink

Filed a bug to fix the document the inconsistencies on the implementation side https://crbug.com/1231268

a-sully avatar Jul 20 '21 20:07 a-sully

Hello, I was wondering if there were any updates on this front? I was just experimenting with uploading / interacting with a folder with a symlink on macOS Sonoma running Chrome 128, and the symlinked file was NOT visible when doing directoryHandle.values().

I was also wondering if there are plans to indicate whether a file entry is a symlink.

Thanks!

pmalacho-mit avatar Sep 27 '24 16:09 pmalacho-mit