For doing manual crossposts, copy-pasting from the displayed-HTML-version of your post into our WYSIWYG editor actually works quite well, and works basically flawlessly about 90% of the time for everything except tables. I’ve put a bunch of effort into making that experience good.
Ok, I had the Markdown editor enabled, and when I tried to paste in HTML all the formatting was removed, so I thought pasting HTML doesn’t work. Can you implement this conversion feature for the Markdown editor too, or if that’s too hard, detect the user pasting HTML and show a suggestion to switch to the WYSIWYG editor?
Also it’s unclear in the settings that if I uncheck the “Markdown editor” checkbox, the alternative would be the WYSIWYG editor. Maybe add a note to explain that, or make the setting a radio button so the user can more easily understand what the two options mean?
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.
For doing manual crossposts, copy-pasting from the displayed-HTML-version of your post into our WYSIWYG editor actually works quite well, and works basically flawlessly about 90% of the time for everything except tables. I’ve put a bunch of effort into making that experience good.
Ok, I had the Markdown editor enabled, and when I tried to paste in HTML all the formatting was removed, so I thought pasting HTML doesn’t work. Can you implement this conversion feature for the Markdown editor too, or if that’s too hard, detect the user pasting HTML and show a suggestion to switch to the WYSIWYG editor?
Also it’s unclear in the settings that if I uncheck the “Markdown editor” checkbox, the alternative would be the WYSIWYG editor. Maybe add a note to explain that, or make the setting a radio button so the user can more easily understand what the two options mean?
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.