Subtle changes, bugs and feedback

It's a pretty clear and annoying bug that has widespread impact and can't be too hard to grok, surely.

Why has @Velocio always been silent on it?

Given a how-to, I'd be happy to get a dev environment up and hack on it myself, but I know that that is not straightforward.

David, throw us a fricken bone here?

I haven't always been silent on it, I recognise it's a bug. But, I'm not a specialist in JavaScript and when Microcosm ran out of money some bugs are harder for me to fix than others, and this one is one of the hard ones for me to fix. I've asked in the past that anyone skilled at JS to look at it, no-one has... so that's where we are.

You're welcome to look into it and create pull request, the code is ultimately in this repo: https://github.com/microcosm-cc/microweb/

Because this is purely client side you don't even need to spin up a full dev environment with database, virtual machines, load balancer, API, etc... all you need do is save a complete web page that has a comment form on it and then edit the JS files according to your debugging.

It's probably this section of the file: https://github.com/microcosm-cc/microweb/blob/master/core/static/js/Markdown.Editor.js#L1526-L1668

If it's not that, then it's maybe this: https://github.com/microcosm-cc/microweb/blob/master/core/static/js/simpleEditor.js#L130-L132

My money would probably be on the latter, but therein lies my failure to fix it... it looks perfectly fine to me. I'm baffled by it.

Not sure what the other messages about, those seem a bit rage-fest. There's no petulance, and I don't understand the context of the last message. If you want to help out that would be great. If you do feel you need a full dev environment I'll pop round and set one up for you, you will need a base Linux system with Virtual Box, git, Go1.6 and vagrant installed.