Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Codidact Meta!

Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.

Post History

66%
+2 −0
Q&A "Body is too short" error when posting middle-click-pasted answer with no changes

Fix pushed. When you save a post, we don't take what you typed into the textbox and convert it to markdown on the server, if we can avoid it (we still have to if the client has JS disabled). There...

posted 2y ago by ArtOfCode‭

Answer
#1: Initial revision by user avatar ArtOfCode‭ · 2021-08-03T11:11:48Z (over 2 years ago)
Fix pushed.

When you save a post, we don't take what you typed into the textbox and convert it to markdown on the server, if we can avoid it (we still have to if the client has JS disabled). There's this live preview below the textbox where the HTML has already been calculated for us, so we might as well make use of that; we actually take that HTML and save it instead of re-processing it. This both saves server time and avoids conflicts or formatting differences between client-side and server-side markdown rendering, so it's good all round.

_However_, that relies on us actually having rendered that markdown client-side at that point. Which, in this case, we hadn't done, because it was only re-rendered on `keyup`, `focus`, and `markdown` events. I've adjusted it to re-render on `paste` and `change` as well, so that should capture most changes.