(In reply to comment #24)
> In addition, it might eliminate the need for at least bugs 228562
My post in bug 228562 comment 0 explains why a toggle button would not solve the
shift+forward issue. First of all, the way that shift+forward is not consistent
with the shift+ behavior of the other compose buttons, so one could argue it
should be changed for consistency's sake if for nothing else. Second, in the
case when a user who defaults to plain text wants to forward an html email with
its html intact, the toggle button would not work because once the forward
button is clicked, the html information is already lost. The only way a toggle
button would solve this problem is if it were on TB's main toolbar, not the
compose window's toolbar, so that the toggle occurred before the forwarding
message is begun. That is of course a possibility, but not yet addressed as an
option by this bug report.
(In reply to comment #24)
> In addition, it might eliminate the need for at least bugs 228562
My post in bug 228562 comment 0 explains why a toggle button would not solve the
shift+forward issue. First of all, the way that shift+forward is not consistent
with the shift+ behavior of the other compose buttons, so one could argue it
should be changed for consistency's sake if for nothing else. Second, in the
case when a user who defaults to plain text wants to forward an html email with
its html intact, the toggle button would not work because once the forward
button is clicked, the html information is already lost. The only way a toggle
button would solve this problem is if it were on TB's main toolbar, not the
compose window's toolbar, so that the toggle occurred before the forwarding
message is begun. That is of course a possibility, but not yet addressed as an
option by this bug report.