41890 - No linewrap in table, when window is maximized

Status: VERIFIED FIXED

(Core :: Layout: Tables, defect, P3)

Description

[Mario Jurkovic]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; m16) Gecko/20000603
BuildID:    2000060320

The text is stretched extremely. It seems like if the browser doesn't jump into
the next line, but it should.

Reproducible: Always
Steps to Reproduce:
1.view the page
2.see the 'error'
3.think about what might be wrong

Actual Results:  It looks bad. Not an actual error, because the information is
still there, but this is bad enough for a geek like me.  :(

Expected Results:  Mozilla should jump into the next line, using a <br> or
something..

Comment 1

[Bernd Mielke]

To reproduce the bug I had to maximize the window under Win98. With a normal
window everything is OK. Renaming and Confirming the bug.

Comment 2

[Mario Jurkovic]

Oh.. I forgot to tell, that this occurs while maximizing the window. To be
honest, this is my first "bug" I reported to Bugzilla and I hope that the
community might understand this silly mistake.. ;)

Comment 3

[Jesse Ruderman]

Attachment: simpler page that shows the bug at lower window sizes

Comment 4

[Jesse Ruderman]

if you load/reload the test case in a skinny window, it wraps correctly until 
you expand the window to a certain width.

Comment 5

[karnaze (gone)]

Attachment: slightly simpler test showing bug with cols=2

Comment 6

[Bernd Mielke]

Adding testcase keyword so this doesn't show up on
the bugathon search page.

Comment 7

[karnaze (gone)]

I'm marking this future since it uses the non standard cols attribute. If 
someone thinks this is an important bug, please express your concerns.

Comment 8

[Tom Mraz]

I can reproduce this bug on Linux nightly 2000090621 build. So someone with
privilegies could change the OS to All.

Comment 9

[Bernd]

similiar to bug 29058. I will look deeper in to the problem. 

Comment 10

[karnaze (gone)]

This has been fixed by Bernd's patch to bug 29058

Comment 11

[Jesse Ruderman]

Looks like bug 56543 got fixed by the patch too :)

Comment 12

[Prashant Desale]

Verified with 2001-020608.