Implementing the same behavior for Markdown is doable, though a bit of annoying engineering effort. I created an issue for it. It’s about as much work as detecting the user pasting HTML, so I think I will try to just do that instead of asking the user to switch to the WYSIWYG editor. (Edit: After checking, the library we use to convert html into markdown is actually server-side only, so that means it’s more work than I expected and maybe the correct choice is to present the user with a dialog. Will have to play around a bit.)
And yeah, it does seem like we should use a radio button instead of a checkbox. Also added an issue for that. We will probably rework the user-settings page at some point in the next few months since it’s been getting pretty crowded and confusing, and so we will probably get to that then.
Ah, yeah. That makes a bunch of sense.
Implementing the same behavior for Markdown is doable, though a bit of annoying engineering effort. I created an issue for it. It’s about as much work as detecting the user pasting HTML, so I think I will try to just do that instead of asking the user to switch to the WYSIWYG editor. (Edit: After checking, the library we use to convert html into markdown is actually server-side only, so that means it’s more work than I expected and maybe the correct choice is to present the user with a dialog. Will have to play around a bit.)
And yeah, it does seem like we should use a radio button instead of a checkbox. Also added an issue for that. We will probably rework the user-settings page at some point in the next few months since it’s been getting pretty crowded and confusing, and so we will probably get to that then.