bblank, your reply (the black part) is very correct but is missing one most important point. Both browsers mentioned here are interpreting the 100% width order differently, actually, I estimate that Netscape is doing it perfectly ok.
The width tag with any percentage specification needs a basis to calculate from. If, as it is on this site, there is no basis explicitly determined, than the browser should use the width required, in the case here the space needed until reaching a carriage return.
Internet Explorer, as it is very obvious, checks first for definition of the 100% order, Netscape does not, according to W3C the screen size needs to be checked to avoid exactly this problem.
For reference the original words in HTML 4.01 which is the given standard today:
A percentage specification (e.g., width="20%") is based on the percentage of the horizontal space available to the table (between the current left and right margins, including floats). Note that this space does not depend on the table itself, and thus percentage specifications enable incremental rendering.
About the nowrap attribute you will find at the very same place the following:
nowrap [CI]
Deprecated. When present, this boolean attribute tells visual user agents to disable automatic text wrapping for this cell. Style sheets should be used instead of this attribute to achieve wrapping effects. Note. if used carelessly, this attribute may result in excessively wide cells.
Just a couple of lines in the Template would avoid the whole problem....