(In reply to Jonathan Kamens from comment #31)
> I'm encountering the problem with TB, not FF.
(oops, sorry, I forgot about that)
> I removed a bunch of "print_to_filename" preferences from prefs.js and that
> made the problem go away.
Ah -- thanks, that's very helpful!
> When I printed to a file after removing those preferences and then exited
> from TB, new "print_to_filename" preferences were not saved in prefs.js.
> This suggests to me that these "print_to_filename" resources are obsolete.
I don't think "obsolete", but they might be only set under certain not-straightforward circumstances. (lots of printing prefs fall into this category, sadly.)
> If so, then shouldn't part of this fix involve removing them, at least
> during a transition period?
(In reply to Jonathan Kamens from comment #31)
> I'm encountering the problem with TB, not FF.
(oops, sorry, I forgot about that)
> I removed a bunch of "print_to_filename" preferences from prefs.js and that
> made the problem go away.
Ah -- thanks, that's very helpful!
> When I printed to a file after removing those preferences and then exited
> from TB, new "print_to_filename" preferences were not saved in prefs.js.
> This suggests to me that these "print_to_filename" resources are obsolete.
I don't think "obsolete", but they might be only set under certain not-straightforward circumstances. (lots of printing prefs fall into this category, sadly.)
> If so, then shouldn't part of this fix involve removing them, at least
> during a transition period?
Possibly.