Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

Problem with &nbsp in formatting

A topic by Alexander Karenovics created Mar 01, 2025 Views: 361 Replies: 8
Viewing posts 1 to 5
(1 edit) (+3)

Dear itch-team,

Since some time I have a huge problem with formatting in my posts wherever on itch.io. Like, some lines consist only of one word, then there would be an automatic line-break, or words seperated randomly. Then I noticed, at least in my gameEditingPage, where I could activate html-view, that the code has been riddled with the & n b s p  tag - manually removing that would fix things. But it's still present in regular comment posts, where I can't simply access the html-view.

Any way I can fix this? Or are there some hidden settings I'm missing?

Thanks!

(4 edits)

Some acknowledgement of this problem would be nice, because the problem persists.

Here is how the text "The quick brown fox jumps over the lazy dog" looks like on itch.io, when I activate HTML view:

Had to screenshot that, lol, cuz the editor assimilates the &-tag, even when using the "code"-tag. ;-)

I can manually delete the &-tag from my own posts in devLogs, but I can not activate HTML-view on regular comments, and the & n b s p - tag is causing all the problems with formatting. Also tried with different browsers and on another PC.

Thank you!

I know an esoteric problem with nbsps and font rendering (0 width for a nbsp). But otherwise, why would nbsps screw up your formatting? You should not "format" anything with spaces. That is not how html is intended.

Had to screenshot that, lol, cuz the editor assimilates the &-tag, even when using the "code"-tag. ;-)

Had to screenshot that, lol, cuz the editor assimilates the &-tag, even when using the "code"-tag. ;-)

Both lines above are a test. Pasted with as text. One was copied from your post. The next was copied from inspect window in the browser, where I can see that it has 7 nbsp and 9 normal spaces. And the next two lines are the same with regular paste.

Had to screenshot that, lol, cuz the editor assimilates the &-tag, even when using the "code"-tag. ;-)

Had to screenshot that, lol, cuz the editor assimilates the &-tag, even when using the "code"-tag. ;-)

(1 edit)

Copy and paste again with past as text or whatever it is called in your browser. That at least deletes the nbsps. The lines above have no nbsp, the lines below both have the nbsps.

Edit: I do not want to edit the above posting to keep the formatting intact. But I now get it. Words connected by nbsp are one big word and that screws up the line breaks on the reader's browser.

(+1)

Didn't realize someone else already made a post about this. Are you also on Firefox, by chance?

https://itch.io/t/4637664/post-bodies-sometimes-use-nbsp-instead-of-spaces-on-fi...

I am not. And if a sentence is made up with nbsps, the rendering browser will not break the lines at the nbsps but at any space available or when the line ends in the middle of the word.

If nbsps are created by simply typing, that sounds very annoying. I know they are sometimes created when copy pasting. And I think by typing two  spaces. If so, there should be a nbsp between two and spaces when you inspect my post.

And if I recally correcly, if you delete characters and then press space. So there might be one in front of So.

Weird... what browser are you on? I don't have this issue on Chromium, only on Firefox.

(+2)

I am not on Firefox, I do not have those nbsps. They only appear if I use two  spaces. I would assume OP is on Firefox.

But since the editbox can use nbsps, this mechanism might be triggered somehow accidentally.  You have 3 in your reply.

(1 edit)

Okay thanks for the insight and all the answers. I just tried typing something in Microsoft Edge, and that indeed seems to resolve the issue for now.

And when typing in firefox, copy/pasting the text into a nother black form (like online notepad), then pasting it back also seems to get rid of the nbsp-tags.

Never thought it was a Firefox issue, oh well .... <3

Thanks all!

This topic has been auto-archived and can no longer be posted in because there haven't been any posts in a while.