Follow-up Comment #20, bug #60927 (group groff): [comment #19 comment #19:] > [comment #13 comment #13:] >> with no discretionary line breaks, > > To reiterate what I said in your savannah feature request, it should not > fall > to the person posting a comment to have to manually insert line breaks to > make > it render sanely. I agree. I would not suggest that editing the offending comment is the _best_ solution here; just that it could offer a possible work-around. > (As I also point out there, the problem doesn't show up in all browsers. So > a > user previewing a comment who sees no problem on their own browser has no > inkling that these line breaks are even needed for readers using other > browsers.) Maybe so, but it _does_ show up in Firefox-142.0, which is the current (latest) Manjaro-1.0 release. >> (e.g. by inserting U+2009 zero width spaces at strategic points), > > (U+2009 is THIN SPACE; U+200B is ZERO WIDTH SPACE) Quite correct. I meant U+200B; U+2009 is a typo, which I would love to correct, but at present, I am denied any opportunity to do so. > A bare URL in a comment serves two purposes: it is displayed in the comment, > and it is also turned into a hyperlink to be clicked on. Adding characters > _within_ the URL to improve its display will sabotage its functionality when > clicked. Which, of course, is why simply editing the URL, as a work-around for the display overflow issue, is far from ideal; it probably _would_ need to be wrapped thus: > A reasonable workaround for this is to wrap the URL in savannah's +nomarkup+[ > ]-nomarkup- markup, > hiding it behind some text. The "some text", behind which the _real_ URL is hidden, _could_ be a copy of the URL, with U+200B, or <wbr> discretionary line break points inserted -- awkward, but it is a feasible work-around. > But a user _should_ be able to post a bare URL and have it work sanely. Agreed. > Hence my opening http://savannah.nongnu.org/support/?111307 to address this. Okay. And interim work, done in respect of this, has improved the overflow situation, but in doing so, it may detract from Brandon's intent to show how horrendously long some savannah URLs can become.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?60927>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
