Ticket #641 (closed Defect: wontfix)

Opened 3 months ago

Last modified 3 months ago

Trac Wiki lines beginning with `monospace`d word are not wrapped

Reported by: Pepo Assigned to: davea
Priority: Trivial Milestone: Undetermined
Component: Undetermined Version:
Keywords: Cc: Pepo

Description

Anytime a text line in Trac Wiki article or Trac Ticket begins with a monospaced word, the remainder of the whole paragaph is continued on the same line infinitely wide behind the article and browser border and is not wrapped anymore. This happens with Internet Explorer 7, but not with SeaMonkey? (possibly everything from Mozilla class) and Safari. The exception is a monospaced word at the beginning of paragraph (1.st line), in this case usually nothing happens, but this paragraph while in preview is indeed broken (or unwrapped) too.

("Component: Web - Forums" is actually wrong, it belongs just to Trac, possibly Wiki formatting generally. Possibly an unrepairable bug of IE7's html interpretation.)

Change History

(in reply to: ↑ description ; follow-up: ↓ 3 ) 05/08/08 14:12:47 changed by Pepo

OTOH, longer sets of monospaced words inside a paragraph are correctly wrapped by IE7, but are attempted to be held together on one line and finally overflowed by Mozilla browsers and Safari. IIRC we were testing this (mis)behavior (among other forum formatting issues) somewhere on Boinc dev forums... (I will find out.)

05/08/08 14:22:55 changed by Nicolas

In Konqueror 3.5.9, I see your "the remainder of the whole paragaph is continued" in the first line, overflowing the description box. In Firefox 2.0.0.14, it wraps to the second line (leaving space after "word," at the end of the first line). However, if that was text longer than can fit in the box, it would overflow in Firefox too (it does in your first comment).

Trac CSS explicitly sets the <tt> element as white-space: pre. (See white-space in the CSS specification for definition). I guess just removing that rule would make things look better.

By the way, lack of wrapping in monospaced boxes is a feature. 

This is supposed to remain in a single line, no matter how long it is. It should not wrap. It's usually used for code, which is better without any wrapping.

(in reply to: ↑ 1 ) 05/08/08 14:32:45 changed by Pepo

Replying to Pepo:

IIRC we were testing this (mis)behavior (among other forum formatting issues) somewhere on Boinc dev forums... (I will find out.)

It was the Testing code thread, but is actually not that relevant here.

Replying to Nicolas:

By the way, lack of wrapping in monospaced boxes is a feature.

Sure, of course, that's what they are for. (BTW, do you know that it's imposible to read one such monospaced boxed line on IE7, if the line is wide enough (like your is) to contain a horizontal scrollbar?)

05/09/08 08:02:12 changed by Ageless

  • owner deleted.
  • component changed from Web - Forums to Undetermined.

Setting component to undetermined as it's about Trac.

05/09/08 08:03:05 changed by Ageless

  • owner set to davea.

Reassigning to David.

05/09/08 09:45:34 changed by davea

  • status changed from new to closed.
  • resolution set to wontfix.

It's a wiki - feel free to fix any formatting problems

05/09/08 10:21:14 changed by Nicolas

We need server access to fix that. There is no way to edit the CSS from the wiki interface...

05/09/08 10:46:15 changed by davea

What CSS change?

05/15/08 10:15:59 changed by Nicolas

Ah, closing tickets without reading them.

Trac CSS explicitly sets the <tt> element as white-space: pre. ... I guess just removing that rule would make things look better.

05/15/08 13:57:39 changed by Pepo

OK.

Is someone around with a wiki to try it out? (.....) I've tried it on Pirates' wiki, the wrapping happens correctly there.

05/15/08 16:02:52 changed by Eric Myers

This would be a Trac bug, not a BOINC bug. I suspect it's an issue with CSS, and might be fixed with a change to the CSS. If you fix it, pass it upstream.

If this page is incomplete or incorrect, please edit it or add it to the wiki to-do list. To do this, you must be logged in; click Login or Register above.