Compose 'editor type' doesn't match type of message body content

[Technetux]

1. save an html draft
2. switch editor type config preference to plain text
3. open the draft

If you're seeing what I'm seeing, the editor type selector should be on plain text and but the actual message content will be showing as html in tinymce.

So there are two options, force the editor to obey your config rule or force the 'editor type selector' to obey the message content's encoding.

If you'd like, let me know which is preferred, I'd be happy to provide a patch.

[alec]

Current solution is intended and prefered.

[ziba]

I'm not arguing, but I want to be sure we're talking about the same aspect of this issue:

The intended and preferred behavior is that in the stated circumstances:

The edit type selector visible on the compose screen indicates that the current message is being composed in text mode, even though the current message is actually being composed in html mode.

Is that correct?

Thanks.

[Technetux]

Exactly Ziba, for example:

Your config preference is set to plain text, you open a draft that was saved as html. The editor type selector will show text but the actual content will be displayed as html. So if you did want to switch to a plain text mode you have to first change the selector to html (which does nothing because it already is html), then switch to plain from html.

[alec]

Replying to Technetux:

Your config preference is set to plain text, you open a draft that was saved as html. The editor type selector will show text but the actual content will be displayed as html. So if you did want to switch to a plain text mode you have to first change the selector to html (which does nothing because it already is html), then switch to plain from html.

This of course is not intended behaviour. Selector value should match editor content. I'm currently unable to reproduce what you've described.

[alec]

Oops, sorry, something is wrong. You're right. I'll work on this.

[alec]

Fixed in [80815d23].