The latest version of Slack has a setting to disable the WYSIWYG editor
In case anyone's interested, here's the Chromium bug(s) that's one of the main reasons the WYSIWYG editor has such issues in Chrome(/Electron):<p>- <a href="https://bugs.chromium.org/p/chromium/issues/detail?id=1029374" rel="nofollow">https://bugs.chromium.org/p/chromium/issues/detail?id=102937...</a><p>- <a href="https://bugs.chromium.org/p/chromium/issues/detail?id=608393" rel="nofollow">https://bugs.chromium.org/p/chromium/issues/detail?id=608393</a><p>- <a href="https://bugs.chromium.org/p/chromium/issues/detail?id=608162" rel="nofollow">https://bugs.chromium.org/p/chromium/issues/detail?id=608162</a><p>The gist of it is that they "canonicalize" the DOM selection when you have two adjacent inline elements, so that it can <i>only</i> ever be at the ending edge of the first inline element. Which makes certain selection states impossible. And on top of that, they don't draw the cursor in the right spot when doing the canonicalization. So for instance, it might look like your cursor is here:<p><pre><code>    <b>one</b>|two
</code></pre>
But it's actually here:<p><pre><code>    <b>one|</b>two
</code></pre>
Drawn in the wrong place. And impossible to put it at the beginning of "two" at all! It's crazy!<p>I don't know how much the take "starring" into account, but it can't hurt to star them in the hopes they're fixed sooner.<p>---<p>Edit: If you want to see the craziness in action, check out this sandbox:<p><a href="https://codesandbox.io/s/amazing-breeze-6elsy" rel="nofollow">https://codesandbox.io/s/amazing-breeze-6elsy</a><p>1. Try to put your cursor at the end of the word "one"<p>2. Try to type a character at the start of the word "two"