Can we get some sort of check that puts a space to break up a long line of text so it doesn't go outside the post box? It already automatically wraps the line when there is a space anywhere in the last line, but not when there are no spaces. See here for a current example of how stupid and annoying this gets.

Also on this idea, can we get automatic breaks when a thread has no carriage returns in it and the preview system (ie, Post too long. Click to view the thread page to see the entire post.) doesn't actually cut it off? Although this isn't as big an issue, there's really no reason it shouldn't already happen. Just put an invisible carriage return or something to that effect when a post goes over 18 lines, if this is possible. See here for an example of how annoying this could get.

I have no knowledge of the engine that does this sort of thing so I will need some experienced Dollars to say if these are possible or extremely time consuming.

We can fix this by adding max width to the reply class.

>>2 Will that affect much else or take a lot of time to do?

lol Water
what a pleb

okay so I want to make sure I'm understanding this right since I'm not the most internet terminology savvy. Is the suggestion to cap the amount of characters a reply can have or simply to fix the problem with the website where replies can extend out of the box. Will doing the latter make the former happen?

If it will, I don't advocate this, simply because while not plentiful, some of the most important and discussion-starting posts throughout the BBS have very long character counts with multiple paragraphs and analyses etc. I think it's counterproductive to limit line counts which would force people to post parts of what was intended to be the same post as multiple posts. For threads involving hyped media, the enter-mash space also works as a way of omitting spoilers for people who notice the thread in the top 10 of the board. The occasions where people break the box width, while annoying, are pretty few and far between anyway.

Then again I'm probably completely misinterpreting what you guys are talking about. Can someone clear this up for me?

http://stackoverflow.com/questions/3058866/how-to-force-a-line-break-in-a-loooooong-word-in-a-div

It's a quick fix that Reltair can do in a second. Just toss in "word-wrap:break-word;" to whatever is holding the text in (I think it's the "replytext" class).

>>4 This version would just break the word before it reaches the end of the div and push it to a new line.

oh okay, yeah, I support this then.

>>4 There's already a cap on the number of characters a reply can have, so, that doesn't solve it. I'm not for that at all. Luckily we have some experienced Dollars among us, >>5 has found a quick fix to add into the site.

Also, it was invented by IE! To quote from the page, "Hey, even a blind squirrel finds a nut every now and then."

Now, the only question is what about the long OP's with no carriage returns that never get cut into a preview? See the Test board for what I mean.

>>8 I don't think it can be easily done tbh. I think kareha is specifically looking for break tags, which means we can't do any invisible returns.

All I can think is to have something run before the post is sent to kareha that changes it by putting in breaks every 1000 characters (if there are no breaks /and/ it's over a certain number of characters).

<>