TYPO3 Core

This is a browser bug.

The stylesheet contains this...
TABLE#typo3-tree TR TD { white-space: nowrap; }
...which means that white-space should not be wraped.

I tested it with Mozilla Firefox and it works.

I'm now closing this bug, but I will reopen it if anyone provides an XHTML compliant fix to the problem.

Sorry thats not my opinion:
Because BE is often better open in IE (RTE) it should work in IE 5.x which does not.
why must BE be XHTML valid?
wrap the items with <nobr> </nobr> is valid XML

danp wrote:

why must BE be XHTML valid?

...because XHTML is the doctype Typo3 is using in the Backend.

wrap the items with <nobr> </nobr> is valid XML

...but it is not valid XHTML.

I think this is a really small issue and is in fact not a Typo3 bug but a bug of IE.

Could you please test more recent versions of IE? What about IE6, is it capable of rendering "white-space: nowrap;"? If so, I'd just advise people to upgrade to that version or use a more standards compliant web brwoser like Mozilla Firefox, they won't regret it.

I remember this problem, too. If there is the chance to make a workaround for this that would be nice.

edited on: 27.06.04 06:45

ingmar wrote:

The stylesheet contains this...
TABLE#typo3-tree TR TD { white-space: nowrap; }
...which means that white-space should not be wraped.

Perhaps a more specific selector could help:

stylesheet.css:
<...>
/* Trees */
TABLE#typo3-tree A { text-decoration: none; }
TABLE#typo3-tree TR TD { white-space: nowrap; }
TABLE#typo3-tree TR TD IMG { vertical-align: middle; }
<...>

I would try to change the firste line:
TABLE#typo3-tree A { text-decoration: none; white-space:no-wrap; }

Thorsten, thanks for your suggestion.
Have you tested it?
It would be nice if it would be possible to resolve this issue by just changing the CSS.

I'm working on a Linux machine without IE so I can't test anything.

I just checked, and it works as expected in MSIE 5.5. But even then, flexforms require MSIE6 IIRC, so...

The fix suggested by Thorsten Kahler doesn't help, too.

Closing this, as it seems to be unimportant and is actually a browser-bug.