Anyone have any links or resources they can share that exemplify best practices for how to gracefully deal with long strings of unbroken text in User Generated Content (UGC)?
For example, let's say a user enters 200 characters of uninterrupted text into a post that has the potential to affect the layout of another user's view by overflowing over other content (Firefox) or by screwing up your floats (IE6). This user could be a jerk that's typed everythinginonelongsentence, a pesky QA-type testing edge cases, or even an innocent user posting a very long URL. The options seem to be: - Apply "overflow: hidden;" to any UGC areas. This would assure that nothing will break a layout. - Shorten and provide ellipsis for longer URLs. (I.e. http://groups.google.com/...) - Automatically insert line breaks when the user submits that data OR when it's pulled from the database. (I.e. break up a very long word, say over 40 chars, with a "-" and a line break.) The first option is a front-end band-aid for a problem that comes from the back-end. Or, maybe I have it all wrong. I'm interested in finding the right balance of presenting and/or scrubbing UGC. Please advise. -RYAN JOY http://twitter.com/atxryan --~--~---------~--~----~------------~-------~--~----~ Our Web site: http://www.RefreshAustin.org/ You received this message because you are subscribed to the Google Groups "Refresh Austin" group. [ Posting ] To post to this group, send email to [email protected] Job-related postings should follow http://groups.google.com/group/Refresh-Austin/web/refresh-austins-job-posting-guidelines. We do not accept job posts from recruiters. [ Unsubscribe ] To unsubscribe from this group, send email to [email protected] [ More Info ] For more options, visit this group at http://groups.google.com/group/Refresh-Austin -~----------~----~----~----~------~----~------~--~---
