Viewing last 25 versions of post by Garden Tinker in topic Report site bugs here

Garden Tinker
Wallet After Summer Sale -
Artist -

The comment-posting system seems to have an odd bug to it, such that it forces a line break under specific circumstances. To the best of my understanding, it happens when placing more than one space at the end of a line that is automatically returned:

[![](https://i.imgur.com/ee3ADQM.png)](https://imgur.com/a/iSPPDGF)

~~~
Please excuse my Latin, but I do so like to wax lorem ipsum when I'm able... For you see, the space is wasted finely, and that alone is worthy of praise.

V.S.

Please excuse my Latin, but I do so like to wax lorem ipsum when I'm able... For you see, the space is wasted finely, and that alone is worthy of praise.
~~~

The forced return is even present in-text when editing the comment afterward, including switching between the Edit and Preview tabs, such that for the example above there are three backspaces needed to connect the comma and the 'a' of 'and', despite only two spaces being used to separate them.

The best I can offer for specs is that I'm using Google Chrome on an outdated Chromebook; I am presuming the browser itself is up to date.

This issue does not appear to happen mid-text otherwise. However, that being said, it would appear that any other instance of more than a single space being used between characters is collapsed into the width of a single space upon posting/previewing, and the same can be said respectively for line-returns. Are these effects intentional, and is it possible to escape them outside of using the code (```/~~~) syntax if so?

My apologies if either of these have already been addressed.
No reason given
Edited by Garden Tinker
Garden Tinker
Wallet After Summer Sale -
Artist -

The comment-posting system seems to have an odd bug to it, such that it forces a line break under specific circumstances. To the best of my understanding, it happens when placing more than one space at the end of a line that is automatically returned:

![](https://imgur.com/a/iSPPDGF])

~~~
Please excuse my Latin, but I do so like to wax lorem ipsum when I'm able... For you see, the space is wasted finely, and that alone is worthy of praise.

V.S.

Please excuse my Latin, but I do so like to wax lorem ipsum when I'm able... For you see, the space is wasted finely, and that alone is worthy of praise.
~~~

The forced return is even present in-text when editing the comment afterward, including switching between the Edit and Preview tabs, such that for the example above there are three backspaces needed to connect the comma and the 'a' of 'and', despite only two spaces being used to separate them.

The best I can offer for specs is that I'm using Google Chrome on an outdated Chromebook; I am presuming the browser itself is up to date.

This issue does not appear to happen mid-text otherwise. However, that being said, it would appear that any other instance of more than a single space being used between characters is collapsed into the width of a single space upon posting/previewing, and the same can be said respectively for line-returns. Are these effects intentional, and is it possible to escape them outside of using the code (```/~~~) syntax if so?

My apologies if either of these have already been addressed.
No reason given
Edited by Garden Tinker
Garden Tinker
Wallet After Summer Sale -
Artist -

The comment-posting system seems to have an odd bug to it, such that it forces a line break under specific circumstances. To the best of my understanding, it happens when placing more than one space at the end of a line that is automatically returned:

>>2757412![https://imgur.com/a/iSPPDGF]

~~~
Please excuse my Latin, but I do so like to wax lorem ipsum when I'm able... For you see, the space is wasted finely, and that alone is worthy of praise.

V.S.

Please excuse my Latin, but I do so like to wax lorem ipsum when I'm able... For you see, the space is wasted finely, and that alone is worthy of praise.
~~~

The forced return is even present in-text when editing the comment afterward, including switching between the Edit and Preview tabs, such that for the example above there are three backspaces needed to connect the comma and the 'a' of 'and', despite only two spaces being used to separate them.

The best I can offer for specs is that I'm using Google Chrome on an outdated Chromebook; I am presuming the browser itself is up to date.

This issue does not appear to happen mid-text otherwise. However, that being said, it would appear that any other instance of more than a single space being used between characters is collapsed into the width of a single space upon posting/previewing, and the same can be said respectively for line-returns. Are these effects intentional, and is it possible to escape them outside of using the code (```/~~~) syntax if so?

My apologies if either of these have already been addressed.
No reason given
Edited by Garden Tinker