[meta] Remove the ability to delete opened files automatically after viewing them

NEW
Unassigned

Status

()

Firefox
File Handling
P3
normal
a year ago
a year ago

People

(Reporter: Paolo, Unassigned)

Tracking

(Depends on: 1 bug, Blocks: 1 bug, {meta})

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

a year ago
When the user chooses to open a file from the handler choice dialog, the file can be viewed in the selected application, but it is marked as read-only and is deleted when the browser exits.

This bug is about removing this ability and always keeping the file on disk after it has been viewed. This might not be an option for files opened from Private Browsing Mode, though.

The Private Browsing Mode case needs to be better specified.

This can only be done if the file is not stored in the system temporary directory, which will be handled by bug 1306335.
Hi, Paolo,

Greetings! May I know the possible target release?
It will be more convenient for us to notify QA to arrange resource.
Thank you. :)
Flags: needinfo?(paolo.mozmail)

Updated

a year ago
Priority: -- → P3
(Reporter)

Comment 2

a year ago
Same answer as bug 1306335 comment 2, with the addition that we would need to specify the Private Browsing Mode case before filing dependencies.
Flags: needinfo?(paolo.mozmail)
(In reply to :Paolo Amadini from comment #2)
> Same answer as bug 1306335 comment 2, with the addition that we would need
> to specify the Private Browsing Mode case before filing dependencies.

Roger that, thanks for the information.
:)
(In reply to :Paolo Amadini from comment #0)
> When the user chooses to open a file from the handler choice dialog, the
> file can be viewed in the selected application, but it is marked as
> read-only and is deleted when the browser exits.
> 
> This bug is about removing this ability and always keeping the file on disk
> after it has been viewed. This might not be an option for files opened from
> Private Browsing Mode, though.
> 
> The Private Browsing Mode case needs to be better specified.
> 
> This can only be done if the file is not stored in the system temporary
> directory, which will be handled by bug 1306335.

Thanks for reminding us to consider about the Private Browsing Mode. These days we have some talks around the issue, and mostly we feel to keep the file in the default/preferred folder instead of storing it to the system temporary. Below are some reasons in our mind, but we could surely discuss them further.

First, saving the file to system temporary was originally intent to support the read-only case but not for the privacy reason. In other words, whether in normal or private browsing mode, the file will be stored in the system temporary as long as the user chooses to open the file link directly with OS application. 

Second, for the Mac users, the file will always be saved to the default/preferred folder. So, if we want to build a consistent download experience across platforms, we should also include that in our discussion.

Finally, and probably the most critical one, lies in the definition as well as the user's expectation of the private browsing mode. In the start page of the private browsing window, it states that Firefox will not save your "temporary files". For most of the users, I wonder how they will interpret this phrase and link it to an "Always open" file. 

If we always save the file to the default/preferred folder, there will be no such a concept of a read-only file. All file will be a download file, the only difference is whether it had been set to be automatically open or not.

What do you think?
Flags: needinfo?(paolo.mozmail)
(Reporter)

Comment 5

a year ago
I think the main point of this bug is the removal of the ability to view file types that the browser cannot handle without storing them permanently on disk.

The location of the file, system temporary directory or preferred downloads directory, is dealt with in bug 1306335, and doesn't seem to make a difference because I've tested on Windows 7 and, even if the file is in the temporary directory, its name is always added to the most recently used list for the application with which it is opened, leaving a visible trace on the user's computer.

Ehsan, given the considerations above and in comment 4, and considering that we already tell the user that downloaded files will be stored on disk, do you think this change would be compatible with Private Browsing Mode? This is part of a bigger user experience redesign in bug 1270405.
Flags: needinfo?(paolo.mozmail) → needinfo?(ehsan)

Comment 6

a year ago
Yes, I think that should be fine.  Thanks for checking!
Flags: needinfo?(ehsan)
You need to log in before you can comment on or make changes to this bug.