request feature: save state between launches

[jpmh]

i run firefox aurora which is updated nearly every day. this is an extreme case, but not dissimilar from one that normal users experience every once and a while, updating their browser and having their "temporary allow" choices lost. perhaps it breaks the concept of "temporary", but can these choices be persisted across relaunches?

[barbaz]

Yeah, that does break the concept of "temporary". -1.

OTOH, having the options to save temporary permissions along with the saved session isn't a bad idea, and would cover your use case.

[therube]

Write a script to export, close, update, import, open ... ?

Not sure offhand if a simple copy of prefs.js - while FF is still open, would correctly reflect Temporary Allows?

If it does, prior to update, copy prefs.js, update, then copy back in the backed up prefs.js.

FF doesn't necessarily need to be open to "update", depending on how you do it.

Hmm... Actually, now with no ftp:// if you wanted to bypass updating "through" the browser... ? ... is that still workable? Some (persistent) URL to pull the current .mar or "latest-aurora" kind of thing.

Could be scripted.