Bugzilla

> Since the security info no longer opens a dialog, but the bubble, the way it works is slightly strange in general.

Ah damn. Funny enough, this would not be an issue if we had stayed with the sliding panel :D

> I think we can leave that for now, possibly remove that menu item in the future.

I think we should remove it right now.
That menu item is pretty useless since we shouldn't show security info if a message doesn't have neither encryption nor signature.
It's a common UX approach to not show actionable items to represent a default state. In our case "default" is non encrypted and non signed.

We should also remove it since that's not really discoverable and we moved the focal point tot he message itself with a dynamic button.

> for non-secure messges, the separator will have to be dealt with since techLabel is not set.

I can manually add that separator when we populate the `techLabel` since the only strings we add are OpenPGP and S/MIME and those are not translated.

> Since the security info no longer opens a dialog, but the bubble, the way it works is slightly strange in general.

Ah damn. Funny enough, this would not be an issue if we had stayed with the sliding panel :D

> I think we can leave that for now, possibly remove that menu item in the future.

I think we should remove it right now.
That menu item is pretty useless since we shouldn't show security info if a message doesn't have neither encryption nor signature.
It's a common UX approach to not show actionable items to represent a default state. In our case "default" is non encrypted and non signed.

We should also remove it since that's not really discoverable and we moved the focal point to the message itself with a dynamic button.

> for non-secure messges, the separator will have to be dealt with since techLabel is not set.

I can manually add that separator when we populate the `techLabel` since the only strings we add are OpenPGP and S/MIME and those are not translated.