[RESOLVED]Import/Export feature doesn't remember last folder

[happy-dude]

Hi,

I am not aware of the regression range of this bug (its been a while since I noticed that it existed... apologies for not finding the time to report it), but with NoScript's Import/Export feature, it does not remember the most recent folder it was navigated to/ acted on.

For example, in a past version, NoScript would remember that the folder you exported to most recently was "My Documents" or the most recently imported was from "Desktop". Now, it always starts in the User's default directory for Windows.

This bug is just a convenience for the user, but its a convenience that I wish to be restored...

I am using NoScript v2.19rc4 on Firefox nighty (Nov 12 build). If there is any more information I can provide, please let me know.

[Tom T.]

I suspect

v 2.1.3rc1
==========================================================================
x Fixed "..txt" (rather than ".txt") being appended as the default file
extension when exporting NoScript's configuration / whitelist (thanks
SeanM for reporting)
x Fixed inital directory uncorrectly initialized by the configuration
export dialog on some platforms (thanks SeanM for reporting)

as it's the most recent change to the export dialog, per the changelog.
Next "find' is in 1.06, which goes back to Fx 2. I might try that, to verify.

I can't find an about:config preference for this, nor in prefs.js file. Giorgio is traveling ATM, but I'd like this fixed too, and be pointed to a user-configurable setting as well as remembering the last. I'll leave him a note. Thanks.

[Tom T.]

In Fx 2.0.0.20, and NS 1.10, which is the last version that supports F2, I still can't find a configurable setting for default export. (Only the whitelist could be exported back then, but no matter.) Nor does it remember it, even in the same browser session. I. e., I export and navigate to Desktop. Close, then export again, but it doesn't remember Desktop -- goes back to the defaults.

Same behavior in both Fx 3.6.24 and Fx 8.0, but at least in F2, the default (for Windows) was My Documents. In the later ones, it's defaulting to C:\Documents and Settings\USERNAME, which seems even less intuitive and less likely to be the user's preference.

Thanks for reporting this. As said, it might take Giorgio a few days to get to it. Appreciate your patience.

[happy-dude]

No problem, I'm glad I can help.

In Fx 2.0.0.20, and NS 1.10, which is the last version that supports F2, I still can't find a configurable setting for default export. (Only the whitelist could be exported back then, but no matter.) Nor does it remember it, even in the same browser session. I. e., I export and navigate to Desktop. Close, then export again, but it doesn't remember Desktop -- goes back to the defaults.

Guess my memory wasn't 100%; I just assumed it remembered the last saved location because... Well, the default location for my backups was in fact the desktop for me (thus, no need for navigating away). Forgive me for this incorrect detail.

(Also, can't wait to see this bug fixed !
Keep up the good work.)

[Tom T.]

Guess my memory wasn't 100%; I just assumed it remembered the last saved location because... Well, the default location for my backups was in fact the desktop for me (thus, no need for navigating away). Forgive me for this incorrect detail.

In the Big Picture, that's a drop of sweat on a flea's nose. No forgiveness required.

(Also, can't wait to see this bug fixed !
Keep up the good work.)

I too, and I'm surprised that it hasn't been reported before -- I rarely use the export feature.
And thank you for the kind words.

[Giorgio Maone]

Investigating, thanks.

[happy-dude]

Has there been any news on this bug report?

Thanks!

[Giorgio Maone]

Has there been any news on this bug report?

Slipped through the cracks, sorry (3 new kinds of security threats coped with in the meanwhile).
Respinning, thanks.

[Giorgio Maone]

Please check latest development build 2.2.3rc4, thanks.

[happy-dude]

A regression cropped up: in Windows 7, the "Save type as" drop down menu has no selection (not even an "All Files" or "Text file" option). This is for the Export option.

It doesn't affect the functionality, but its basically a sorting mechanism for the folders. Otherwise, things work fine and the directory is saved.

[Tom T.]

A regression cropped up: in Windows 7, the "Save type as" drop down menu has no selection (not even an "All Files" or "Text file" option). This is for the Export option.

It doesn't affect the functionality, but its basically a sorting mechanism for the folders. Otherwise, things work fine and the directory is saved.

Confirmed on Win XP, Fx 3.6.24 and Fx 8.01, NS 2.2.3rc4 on both.

However, since you need to enter a title anyway, I just entered "export.txt", which doesn't need the "Save as type" setting at all. It reads the file extension properly, and saves it instantly to the desired destination -- in this case, the desktop. (And that destination is sticky for the next time.)

This also worked with extensions .rtf and even export.odt (Open Office text doc, like MS Word). All saved in their specified format.
So the second window and dropdown actually seem redundant, and one more needless click, FWIW.

ETA: Same with Import. Navigate to the folder where it's located, enter file name with extension, works great.

[dhouwn]

A regression cropped up: in Windows 7, the "Save type as" drop down menu has no selection (not even an "All Files" or "Text file" option). This is for the Export option.

I see this already in rc2.

This also worked with extensions .rtf and even export.odt (Open Office text doc, like MS Word). All saved in their specified format.

You mean with the specified file ending, the content of the file is of course always the same (file where the entries are separated using line breaks and UTF-8-encoded without a marker).

[Tom T.]

This also worked with extensions .rtf and even export.odt (Open Office text doc, like MS Word). All saved in their specified format.

You mean with the specified file ending, the content of the file is of course always the same (file where the entries are separated using line breaks and UTF-8-encoded without a marker).

Not quite. I meant that if you entitle it with the Wordpad extension, it's saved as a Wordpad doc. If you use the .odt extension, it's saved as an OO doc. So the dropdown selector for "Save as type" is indeed redundant, in that the extension chosen by the user is honored by the navigation/dialog box.

But yes, the format is preserved in these three test cases of file types.

[dhouwn]

Ah OK, it's just that with "file format" I associated the content of the file, not how it is recognised by the OS. And yes, since the empty drop-down list apparently is equivalent to no file ending or "*.*" it just saves it with this file ending and no other.
BTW: If you put "filename.ending" in quotes it always saves it with this particular file ending (works also if you want no ending) and for filtering you can write a file name with wildcards (e.g. "*.txt") and click save / press enter and the window will stay open filter the displayed files accordingly.

[Tom T.]

BTW: If you put "filename.ending" in quotes it always saves it with this particular file ending

Nice tip, although the original default was that exports would save to .txt by default in Windows. Which was the subject of a thread two months ago, that it was saving as txt, but with two dots instead of one: whitelist..txt. Resolved the extra dot. The OP noted that the filetype window was empty, but if you entered no extension, it defaulted to .txt. He was on XP, like me; can you test and confirm this default on Win 7?

(works also if you want no ending)

Don't understand why I would want no ending. Only "HOSTS" comes to mind as a common file without an extension, but I thought we're still talking about NS export? (I uncheck the folder option "Hide extensions for known file types", as a safety precaution.)

and for filtering you can write a file name with wildcards (e.g. "*.txt") and click save / press enter and the window will stay open filter the displayed files accordingly.

I didn't understand this, either, but now I do - we're talking about *import* now, right? Useful if the save-to location contains many different files, of many different types.