See bug 254931 comment 1. I think that Forward Inline, like Edit As New,
probably should default to opening in the same mode as the original message --
if you got an HTML message, forwarding it should result in an HTML composition
regardless of the setting. (The information from Neil that I quote at that
comment implies that there is some basic similarity between Forward Inline and
Edit As New already, so perhaps this is in fact what's intended.)
Then, as long as the shift+tool hack is being relied on, Shift+Forward would
reverse the expectation; and when/if the in-window mode-switch is in place, the
original HTML information shouldn't be lost on a forward unless the user
explicitly forced it. However, per bug 293649, there is some *other* problem
with Forward Inline where at least some formatting is getting discarded even
when the compose window is HTML.
See bug 254931 comment 1. I think that Forward Inline, like Edit As New,
probably should default to opening in the same mode as the original message --
if you got an HTML message, forwarding it should result in an HTML composition
regardless of the setting. (The information from Neil that I quote at that
comment implies that there is some basic similarity between Forward Inline and
Edit As New already, so perhaps this is in fact what's intended.)
Then, as long as the shift+tool hack is being relied on, Shift+Forward would
reverse the expectation; and when/if the in-window mode-switch is in place, the
original HTML information shouldn't be lost on a forward unless the user
explicitly forced it. However, per bug 293649, there is some *other* problem
with Forward Inline where at least some formatting is getting discarded even
when the compose window is HTML.