Bug desriptions only wrap on whitespace
Bug #6126 reported by
Stuart Bishop
This bug report is a duplicate of:
Bug #929: Long words (such as URLs) overflow columns.
Edit
Remove
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
New
|
Medium
|
Unassigned | ||
Bug Description
When a particularly long string is needed in a bug description or comment
that is wider than the available space, we have no choice but to break the
the string and wrap it.
Launchpad, however, doesn't make this choice and instead allows the string
to pollute the neighbouring regions. This can be seen at
https:/
affects /products/malone
--
Stuart Bishop <email address hidden>
http://
Attachment: signature.asc
Type: application/
URL: http://
Revision history for this message
| James Henstridge (jamesh) wrote | #1 |
To post a comment you must log in.
The fix for this would be in the fmt:text-to-html routine. There are a few choices here:
1. use the non-standard <wbr> tag (word break). This is supported by all major web browsers. Has the side effect that double click select won't select the entire word if it contains a word break.
2. use the zero width space character (​). Apparently causes some display issues in IE.
3. use the soft hyphen character (­ or ­). This character is supposed to only display when at the end of a line, and act as a word break. Unfortunately, it isn't properly supported by Mozilla (doesn't break words).
http://
https:/
4. use actual space characters. Works with every browser, but looks ugly and can change the meaning of the text.
A rundown of the compatibility for the various word breaking methods can be found here:
http://
In both cases, we'd need to make some decisions about where to place such breaks. How long can a word get before we break it? Do we just break words at a particular number of characters, or try to inteligently hyphenate the text?