Duong Nguyen: This fix introduces a bug in which typed text followed by <return> will be replaced by a post reference without allowing me to choose (on Chrome on a Mac). This is a problem when using ### Markdown to write section headers. E.g., I type ### Good examples <return> and it replaces it with ###183 Ditto for ###. Good examples<return>, but ###: Good examples it will accept, then I can go back and delete the :.

Very frustrating to have a long sentence vanish, and I can't undo. On browsers where it does pop up options, that is also frustrating because I can't see what I'm typing behind the pop-up.

Jack Snoeyink: I see the problem. So it seems to be recognizing ### as a post reference, is that correct? We'll make a fix so that it does not recognize header markdown as a post reference.

Duong Nguyen: That is not the only problem: even after one types a post reference, it is still looking to complete the reference and will wipe out text typed after if there is a match to some post. Behavior verified on Mac & Windows Chrome, and Windows Edge. Here is a brief loom video: https://www.loom.com/share/23e7f7dc487b44d18f5c69da0698a637

Let me underscore the severity of this for Tade Oyerinde: I would be very happy if the fix was reverted; I can live with needing to put some extra spaces around punctuation. I cannot live with sentences vanishing with no way to undo.

Jack Snoeyink: We're on it. A fix will be out by end of day tomorrow.

Jack Snoeyink: Small update on this. We found the issue and made the fix for it. However, we won't be able to deploy the new changes until the end of the week. There are some other issues we need to fix first before we can push this update out. So sorry about that.

Jack Snoeyink: It should be fixed now. Please make sure to refresh your browser.