Text editor turns spaces into non-breaking spaces, resulting in bad line breaks
Describe the bug
Nearly all spaces when typing into the itch text boxes become non breaking spaces. It occurs when typing into the text box on itch for page creation, comments, or forum posts - most spaces are invisibly turned into & nbsp; (note: no space between & and n, just having trouble typing it without it turning into the non-breaking space in markdown). The only way around it is to turn on html mode and find-and-replace them with regular spaces or to copy text from a plain text editor. The spaces do not look different in the regular text editor mode (non HTML) and are completely invisible for comments without the HTML toggle.
To Reproduce Steps to reproduce the behavior:
- Open an itch.io page
- Type text into the text box for the description (e.g. "blah blah blah testing for the non-breaking spaces"
- Switch to HTML
- Text has random
inserted
Expected behavior The text editor should not insert non-breaking spaces when a regular space was typed.
Screenshots Entered text, as seen in non-html mode:
Resulting html:
Desktop (please complete the following information):
- OS: Windows 11
- Browser: Firefox
- Version: 135.0.1
Additional context
I can confirm this problem has occurred to at least 4 other developers. For me it seems to affect all text I type in itch, whether it be comments, forum posts, or description boxes. The only way around it is to find-and-replace the HTML & nbsp; with a regular space, or to paste text in from an external editor. It started occurring around two weeks ago for me.
I've been getting increasingly furious over this when writing comments on jam games. Please fix this. I'm tired of having to copy paste the content of my comment to a separate text field to then paste it back in order to not have completely messed up line breaks.
This appears to be a duplicate of an issue I placed. #1730
But yeah, this is still an issue.
Commenting to add on that this is still an issue, and infuriating to deal with on longer posts. I've found that using a find and replace tool can work (although you have to make a small change in the editor before saving, otherwise it won't stick), but that this needs to be done at all is bizarre