Please correct me if this does work as intended, but as far as I understand Data.pm, breakHtml() should take care of breaking up comments in about all cases.
I was also unable to reproduce this behavior locally with a standalone (mock-up) version using code from Data.pm in CVS. Examining both URLs that aren't broken up properly it seems as if ampersands and urlencoded characters were considered "breaking tags". Due to obvious reasons I didn't want to test this theory by actually posting a comment, but at least using the preview button I can break the horizontal scrolling of the preview and evade the "That's an awful long string of letters there" lameness filter using a string like
xxxxxxx&xxxxx&xxxxxx&[....]
or
xxxxxxx%2dxxxxx%2dxxxxxx%2d[....]
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Firefox 2.0.0.6, Konqueror 3.5.7 and Mozilla 1.7.13 on FreeBSD 6.2-RELEASE, logged in or not, even on new browser profiles that have never seen slashdot before. I could get some friends to reproduce it (Linux i686; en-US; rv:1.8.1.6 Gecko/20061201 Firefox/2.0.0.6 (Ubuntu-feisty), Konqueror 3.5.7 and Firefox 2.0.0.3 on Gentoo) and according to the comment "congratulations on breaking slashdot" attached to one of the posts with a long URL, other people are also affected.
In the meanwhile I had an opportunity to view those comments in Internet Explorer 6 and could see they were rendered properly, although the long URLs were neither broken up by spaces nor did they have <nobr><wbr></nobr> in between. I'd say depending on whether this is behavior intended or not it's either a browser bug or an issue in the code.
File Added: slashdot-scrolling.jpg
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=88484
Originator: YES
Horizontal scrolling broke again at http://games.slashdot.org/comments.pl?sid=326845&cid=20963375 .
Please correct me if this does work as intended, but as far as I understand Data.pm, breakHtml() should take care of breaking up comments in about all cases.
I was also unable to reproduce this behavior locally with a standalone (mock-up) version using code from Data.pm in CVS. Examining both URLs that aren't broken up properly it seems as if ampersands and urlencoded characters were considered "breaking tags". Due to obvious reasons I didn't want to test this theory by actually posting a comment, but at least using the preview button I can break the horizontal scrolling of the preview and evade the "That's an awful long string of letters there" lameness filter using a string like
xxxxxxx&xxxxx&xxxxxx&[....]
or
xxxxxxx%2dxxxxx%2dxxxxxx%2d[....]
Logged In: YES
user_id=88484
Originator: YES
Happened again.
http://hardware.slashdot.org/comments.pl?sid=336921&cid=21085599
Logged In: YES
user_id=3660
Originator: NO
What browser, version, and platform?
Logged In: YES
user_id=88484
Originator: YES
Firefox 2.0.0.6, Konqueror 3.5.7 and Mozilla 1.7.13 on FreeBSD 6.2-RELEASE, logged in or not, even on new browser profiles that have never seen slashdot before. I could get some friends to reproduce it (Linux i686; en-US; rv:1.8.1.6 Gecko/20061201 Firefox/2.0.0.6 (Ubuntu-feisty), Konqueror 3.5.7 and Firefox 2.0.0.3 on Gentoo) and according to the comment "congratulations on breaking slashdot" attached to one of the posts with a long URL, other people are also affected.
In the meanwhile I had an opportunity to view those comments in Internet Explorer 6 and could see they were rendered properly, although the long URLs were neither broken up by spaces nor did they have <nobr><wbr></nobr> in between. I'd say depending on whether this is behavior intended or not it's either a browser bug or an issue in the code.
File Added: slashdot-scrolling.jpg
Screenshot of broken scrolling
Logged In: YES
user_id=88484
Originator: YES
Another occurrence with user commenting on the bug
http://slashdot.org/comments.pl?sid=353135&threshold=-1&cid=21266629