1839894 - The read only attribute is not respected when attempting to import passwords from a CSV file

Status: RESOLVED INVALID

(Firefox :: Migration, defect)

Description

[Anca Soncutean, Desktop QA]

Found in

• Nightly 116.0a1

Affected versions

• Nightly 116.0a1

Affected platforms

• Windows 10

Preconditions

• Ensure “signon.management.page.fileImport.enabled" is set on True in about:config.
• Have a valid csv file that has read only permission (Properties - check Read-only attribute - Apply - OK)

Steps to reproduce
About:logins path:

1. Open Menu - Import from a File.. - select the CSV from precondition - click the Open button
2. Observe behavior

About:preferences path:

1. Open Import Data - select Passwords from CSV - select the CSV from precondition - click the Open button
2. Observe behavior

Expected result

• About:logins path - "Unable to Read File: Firefox does not have permission to read file. Try changing the file permissions.” error message should be displayed.
• About:preferences path - “We weren’t able to read the selected file. Pick another file.” error message should be displayed.

Actual result

• About:logins / About:preferences path - The CSV content is imported successfully, without any error.

Regression range

• Not a regression; about:preferences path was recently introduced, note though that for the about:logins path, the issue goes way back to Fx 88.

Additional notes

• Not reproducible on mac

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

:asoncutean, if you think that's a regression, could you try to find a regression range using for example mozregression?

Comment 2

[Molly Howell (she/her) (mostly inactive)]

It sounds like there's been some confusion here; the read-only attribute should prevent the CSV file from being written to, it does not prevent reading from it. That's why it's called read-only, because then you can only read and not write. If the desire is to make the file unreadable, then the read permission needs to be revoked from the Security tab in the file properties.

Comment 3

[Anca Soncutean, Desktop QA]

Yes, indeed, I've made a mistake here. Sorry for the confusion. It behaves as it should with the right approach. I will mark it accordingly.