(Is that long enough? :) We should <nobr> the date stuff. (As discussed in previous bugs regarding wrapping, |white-space: pre;| isn't portable enough yet)
OK, that wasn't long enough... One issue with this is what happens if you have a narrow browser window. Theres no |white-space: break=if-aesthetic;| css property.... Thoughts?
Why is it such a big deal if it wraps? When it does, you get: Last modified: 2002-11-11 06:11 which isn't so bad. It has to be _really_ cramped to get: Last modified: 2002-11-11 06:11 I don't think this is a bug, really. Gerv
The User Interface component now belongs to Gerv. Reassigning all UNCONFIRMED and NEW (but not ASSIGNED) bugs currently owned by Myk (the previous component owner) to Gerv.
Reassigning back to Myk. That stuff about Gerv taking over the User Interface component turned out to be short-lived. Please pardon our confusion, and I'm very sorry about the spam.
I get: Last modified: 2003-07-19 12:06 PST which should be (if necessary): Last modified: 2003-07-19 12:06 PST The CSS rule is portable enough, especially by now and for a nit like this, and should be used in lieu of nowrap.
Actually, I'm pretty much against using nbsp, as it makes it impossible for the browser to do a nice wrap that suits the window size. In a small window (or when you use a large font), if you make the Last Modified date unwrappable, the summary would be wrapped instead, which could look funny instead. And sometimes, when using nbsp extensively, a horisontal scroll bar appears, as the browser cannot wrap one or more of the lines. This makes the whole page be wider than 100%, making all text on the page wider that 100%, in which case you have to use the horisontal scrollbar extensively while reading the page. Furthermore, I really don't see the problem in this wrapping: Last modified: 2002-11-11 06:11 Apart from the fact that it rarely occurs, I still find it very readable when it occurs.
This bug has not been touched by its owner in over six months, even though it is targeted to 2.20, for which the freeze is 10 days away. Unsetting the target milestone, on the assumption that nobody is actually working on it or has any plans to soon. If you are the owner, and you plan to work on the bug, please give it a real target milestone. If you are the owner, and you do *not* plan to work on it, please reassign it to firstname.lastname@example.org or a .bugs component owner. If you are *anybody*, and you get this comment, and *you* plan to work on the bug, please reassign it to yourself if you have the ability.