We’re integrating TypeScript into the build system soon, but if it had already been here, it would have caught that mistake. Oops.
Image width must be greater than 0
Image height must be greater than 0
Image width must be greater than 0
Image height must be greater than 0
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.
my:faves
and (optionally) my:upvotes
Almost all the images I’ve posted in comments in the past are broken now …
[byte\[\]](/forums/meta/topics/report-site-bugs-here?post_id=5172263#post_5172263)
#post_<id>
part and only leads to https://derpibooru.org/forums/path/to/topic-title?post_id=<id>
, which stays at the top of the page and doesn’t jump to the post.[the full url](https://derpibooru.org/forums/meta/topics/report-site-bugs-here?post_id=5172263#post_5172263)
?post_id=5172263#post_5172263
)However, if you put in exactly the same link as the full url including https://derpibooru.org, the link somehow drops the#post_<id>
part
(On that note: Why does the url contain the post id two times??post_id=5172263#post_5172263
)
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: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.
Help fund the $15 daily operational cost of Derpibooru - support us financially!