Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Handling of symbolic links (symlinks) #113

Open
foolip opened this issue Nov 20, 2019 · 4 comments
Open

Handling of symbolic links (symlinks) #113

foolip opened this issue Nov 20, 2019 · 4 comments
Labels
clarification Standard could better describe desired behavior

Comments

@foolip
Copy link
Member

foolip commented Nov 20, 2019

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 foolip mentioned this issue Nov 20, 2019
Closed
5 tasks
@mkruisselbrink mkruisselbrink added this to the V1 milestone Apr 10, 2020
@ftreesmilo
Copy link

@mkruisselbrink any update on this?

@mkruisselbrink
Copy link
Contributor

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 mkruisselbrink removed this from the V1 milestone Jul 20, 2021
@mkruisselbrink mkruisselbrink added the clarification Standard could better describe desired behavior label Jul 20, 2021
@a-sully
Copy link
Collaborator

a-sully commented Jul 20, 2021

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

@Jaifroid Jaifroid mentioned this issue Aug 8, 2022
Closed
Sammy-T added a commit to Sammy-T/snow-cms that referenced this issue Jun 11, 2024
@Sammy-T
Remove 'pnpm' warning
fffd155 
The pnpm issue seemed to have been caused by the browser's File System Access API's inability to handle symlinking. The issue was circumvented when I configured directory skipping.

see: WICG/file-system-access#113
@pmalacho-mit
Copy link

pmalacho-mit commented Sep 27, 2024 •
edited
Loading

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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
clarification Standard could better describe desired behavior
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@mkruisselbrink @foolip @ftreesmilo @a-sully @pmalacho-mit