We want to move to a model on all platforms where user data is not stored in the application area. This is the Linux-specific ticket. See #13252 (moved) for the original, Mac-specific ticket.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items
0
Show closed items
No child items are currently assigned. Use child items to break down this issue into smaller parts.
Linked items
0
Link issues together to show that they're related.
Learn more.
See #20497 (moved) for a related ticket.
Also, if there is a chance that the user data might be stored in a shared location such as the user's home directory, then we need to account for the last issue raised by Arthur in ticket:13252#comment:57 after all, i.e., we may need to embed the app path in the update directory (like we do on OSX) in order to ensure that the update history is partitioned.
Under this model, how does updating work? If it moves beyond "Download the MAR and update it like upstream firefox", then I'd need documentation on how to replicate the other steps for the whole "the sandboxing helper needs to handle installation/updates" use case.
Something I can set at runtime to force existing behavior would also work I guess...