3 ms·

Short answer: No. Long answer: Nooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo

Short answer: No. Long answer: Noooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo.

barrkel 15y ago
There needs to be a fix for this attack. I suggest inserting spaces in very long sequences of non-space characters.
- deleted 15y ago
  [deleted]
- tikhonj 15y ago
  I think an easier fix would be setting the maximum width of each comment to something (maybe in % and dependent on the level of nesting) and letting overflow be visible. That should let all the other comments wrap normally without complicated logic or changing the behavior of posts like this. Of course, I haven't done much CSS in a while, so I don't remember the particulars, but the important point is that you can fix this with CSS (I think).
  - barrkel 15y ago
    The way I see it, the alternatives to forcibly wrapping are: * Overflow that extends into the page margins (looks ugly) and either forces the browser to show a scrollbar, or forces the user to resize the window to view the full text (which may not even be possible). * Overflow that is contained within the margins, and can only be read by use of nested scrollbars (I hate those, don't you?) or again, by resizing the window to widen the content column width (again, not always possible). Of all the options, I think forced wrapping is the most visually pleasing. Whether that can be done with CSS I don't know. I do know that introducing spaces will do it. Other techniques may involve e.g. Unicode soft hyphen, see e.g. http://blogs.msdn.com/b/oldnewthing/archive/2011/12/13/10246957.aspx http://blogs.msdn.com/b/oldnewthing/archive/2011/12/13/10246... Of course, another way to do it is to simply reject the input. That's the way Slashdot does it.
    - zem 15y ago
      > Of course, another way to do it is to simply reject the input. That's the way Slashdot does it. huh. i'm pretty sure i remembered slashdot inserting spaces to break up pagewidening text, but it's been a good many years so i could be wrong.
      - barrkel 15y ago
        I thought so too. I think that's where I got the idea from; that's why I went off and tested it, but it turns out that's not what they do anymore.
- zem 15y ago
  slashdot faced this exact problem back in the day, and iirc inserting spaces was what they settled on.

barrkel 15y ago

There needs to be a fix for this attack. I suggest inserting spaces in very long sequences of non-space characters.

deleted 15y ago
[deleted]
tikhonj 15y ago
I think an easier fix would be setting the maximum width of each comment to something (maybe in % and dependent on the level of nesting) and letting overflow be visible. That should let all the other comments wrap normally without complicated logic or changing the behavior of posts like this. Of course, I haven't done much CSS in a while, so I don't remember the particulars, but the important point is that you can fix this with CSS (I think).
- barrkel 15y ago
  The way I see it, the alternatives to forcibly wrapping are: * Overflow that extends into the page margins (looks ugly) and either forces the browser to show a scrollbar, or forces the user to resize the window to view the full text (which may not even be possible). * Overflow that is contained within the margins, and can only be read by use of nested scrollbars (I hate those, don't you?) or again, by resizing the window to widen the content column width (again, not always possible). Of all the options, I think forced wrapping is the most visually pleasing. Whether that can be done with CSS I don't know. I do know that introducing spaces will do it. Other techniques may involve e.g. Unicode soft hyphen, see e.g. http://blogs.msdn.com/b/oldnewthing/archive/2011/12/13/10246957.aspx http://blogs.msdn.com/b/oldnewthing/archive/2011/12/13/10246... Of course, another way to do it is to simply reject the input. That's the way Slashdot does it.
  - zem 15y ago
    > Of course, another way to do it is to simply reject the input. That's the way Slashdot does it. huh. i'm pretty sure i remembered slashdot inserting spaces to break up pagewidening text, but it's been a good many years so i could be wrong.
    - barrkel 15y ago
      I thought so too. I think that's where I got the idea from; that's why I went off and tested it, but it turns out that's not what they do anymore.
zem 15y ago
slashdot faced this exact problem back in the day, and iirc inserting spaces was what they settled on.