Created by Jukka Santala (donwulff@iki.fi) on Wednesday, April 8, 1998 5:46:05 PM PDT Additional Details : This problem is already known to Netscape, since quick debugging turned up: /* * BUG BUG: We''re restoring the break state to the beginning of the buffer - ie * to before the space we skipped above. We need to fix the space skipping mechanism * to remove this case (we can go into an infinite loop here if there''s not enough space * for the first word). * * Should be able to have a new flag "canSkipSpace" but then actually don''t skip it. Then * if the line does fit and it''s at the beginning, we can skip the space. lo_FindLineBreak * should probably be the one to do this work so that the width we get back is correct. */ This text appears in LO_Layout_Text_Block() of lib\layout\leytext.c, 6486 lines into it to be exact. A quick way to skip it for stable build is to quote out the "continue" statement at the end of the function, altough this will cause at the very least bad formattign and potential loss of readability/text in the browser. However, for debugging and testing etc. I find this more desirable than an all-out crash while waiting for a correct patch, which I assume by the remark in the source-code Netscape is working on if hasn''t already finished. To actually see this bug in action (Well, as much as there''s to see in a hanging up browser) try the page http://www.cnet.com/Content/Builder/Authoring/Xml20/ss04.htm l - warning, make sure you have nothing important unsaved/in process in Mozilla, because there''s no graceful way out of this. Updated by Nisheeth Ranjan (nisheeth@netscape.com) on Sunday, April 26, 1998 6:31:54 PM PDT Additional Details : Actually, Jukka, its good that you reported this problem because the engineer who wrote this comment was a contractor and is no longer at Netscape. So nobody at Netscape was dealing with this problem. Am assigning this bug to myself... Thanks again, Jukka.

Jukka, have you been seeing this problem in the latest builds. I recall that this got fixed a while back. I tried the CNET URL that you posted but the content is no longer available. Please mark this bug fixed if you no longer see this behavior. Thanks.

I had the file referred in the URL saved for later reference; it doesn't cause any unexpected behaviour on 1998-09-04 anymore, so I assume the problem has been fixed. You ask me to mark it fixed, but did it already yourself, so I leave the status untouched given I'm not familiar with the Mozilla QA process.

asking donwulff@iki.fi to please verify bug

As noted earlier, checked against saved HTML file and I'm not able to reproduce it anymore - just tried again with latest build. The page looks great, tho' ;)