1427206 - chrome directory can no longer be symlinked in Quantum

Status: UNCONFIRMED

(Toolkit :: Startup and Profile System, defect)

Description

[sebastien.barre]

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:57.0) Gecko/20100101 Firefox/57.0
Build ID: 20171206182557

Steps to reproduce:

For the longest time until version 57 (Quantum), the chrome directory in my user profile has been a symlink to another directory, which allows me to revision-control and synchronize its contents.

I updated to 57 only to notice that the styles in my chrome/userContent.css are no longer applied.

I tested this by creating a normal chrome directory instead of the symlink, and putting a copy of my userContent.css file there. I restarted 57 and sure enough, the styles were loaded and applied properly. 

Note that userContent.css can not be a symlink either; I had symlinked the chrome directory to work around this issue originally, back then. So there is no way to revision control any of these files now.


Actual results:

The styles in my chrome/userContent.css are no longer applied.



Expected results:

57 should look into the chrome directory even if it is a symlink, so styles in chrome/userContent.css are applied again.

Comment 1

[Masatoshi Kimura [:emk]]

I guess this is a sandbox restriction. Although the chrome directory is whitelisted, it will not grant access to the symlink target.

Comment 2

[ELLIOTTCABLE]

Am I to understand that the only work-around for this (at least, with syncing services that cannot select multiple sync-directories, like Dropbox), is to disable sandboxing entirely? )=