(In reply to comment #25)
> (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.
(In reply to comment #25)
> (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.
quite right - my bad
should this be depends on bug 140800?