On loading a file from the file browser, all paths become absolute
All paths to files and directories must be "below" the app's root directory. The in-app file browser makes it possible to change the working directory, whose path is assumed to be relative to the app's root path. Relying on this assumption, the file browser determines whether to include the parent directory ".." in the current directory listing or not. If the current working directory is at the root, the parent directory is not available.
Problem: After loading a second file by double-clicking on a valid data file in the file browser, the current directory becomes a full path and the parent directory is still available when reaching the root directory. On attempting to go one level up, a SecurityAlert
is emitted.
Expected behavior: The parent directory ".." is not displayed at the root directory.
The jail is robust and cannot be escaped, therefore this issue is minor.