Bugzilla

(In reply to Alessandro Castellani (:aleca) from comment #11)
> - Only on encrypted messages (recommended)

This option can be set indepenently of the encrypt by default setting. So we need to define what will happen while working inside composer.

If this selection is combined with "do not enable encryption by default", then on composer open time, signing is disabled.

What happens if the user manually enables encryption for the individual message. We'd have to automatically enable signing.

What happens if the user then decides to disable encryption again, in the same message? We'd also disable signing automatically, right?

The above is what happens if the "first" action inside the composer window is to enable encryption.

But, if the first action made by the user is to "enable signing"? If the user enables encryption as a second step, we can keep signing enabled, that's aligned with the default pref. But, if the user then disables encryption again? In that scenario, I'd keep the signing enabled, and don't disable it, because the user had manually enabled signing.

Does that make sense, or does it seem confusing?


> And underneath we can have a description stating: "You can modify these options independently when composing a new message" or something like that to let the user know that these are just the default settings, but can be manipulated on a per-message base.
> 
> We could consider also adding some text feedback when the user changes these settings in the composer window, something like:
> "Your digital signature was removed for this message, this won't affect your default settings for future messages."

It may be complex to decide in which situations a warning message is appropriate.

(In reply to Alessandro Castellani (:aleca) from comment #11)
> - Only on encrypted messages (recommended)

This option can be set indepenently of the encrypt by default setting. So we need to define what will happen while working inside composer.

If this selection is combined with "do not enable encryption by default", then on composer open time, signing is disabled.

What happens if the user manually enables encryption for the individual message? We'd have to automatically enable signing.

What happens if the user then decides to disable encryption again, in the same message? We'd also disable signing automatically, right?

The above is what happens if the "first" action inside the composer window is to enable encryption.

But, if the first action made by the user is to "enable signing"? If the user enables encryption as a second step, we can keep signing enabled, that's aligned with the default pref. But, if the user then disables encryption again? In that scenario, I'd keep the signing enabled, and don't disable it, because the user had manually enabled signing.

Does that make sense, or does it seem confusing?


> And underneath we can have a description stating: "You can modify these options independently when composing a new message" or something like that to let the user know that these are just the default settings, but can be manipulated on a per-message base.
> 
> We could consider also adding some text feedback when the user changes these settings in the composer window, something like:
> "Your digital signature was removed for this message, this won't affect your default settings for future messages."

It may be complex to decide in which situations a warning message is appropriate.