I was so supprised to find Mozilla (3/29/99) has troubls on my own web page created 100 years ago. Mozilla does not seem to be starting a line for <dt> .. </dt> syntax. Every other browser I have used works correctly with it. Don't laugh at the page it realy needs updating.

Can someone please verify that this problem still exists? It looks identical to 4.5 to me.

Hmmm, Rick I am still having the problem, In the case of the url in question http://users.ipa.net/~asj/ . Picked up the 4/2/99 build of Win32 build. Let me give you and example of what I see..... Every thing is fine through the multi colored bar (gif). Then right after that is a red dot (gif) followed by the words "Heifer Project and ...." This information and more all appears on the same line as the color bar. No carage returns. The widder I make the screen the more that appears on the first line. I was only able to make the screen so wide, but it looked like all of the colored gif balls I have that act as bullets would all appear on the same line (no CR/LF). On Netscape or IE browsers each dot is the start of a differnt line like a bullet. Not sure why you would not see it. Can anyone else test?

Hmmm, Rick I am still having the problem, In the case of the url in question http://users.ipa.net/~asj/ . Picked up the 4/2/99 build of Win32 build. Let me give you and example of what I see..... Every thing is fine through the multi colored bar (gif). Then right after that is a red dot (gif) followed by the words "Heifer Project and ...." This information and more all appears on the same line as the color bar. No carage returns. The widder I make the screen the more that appears on the first line. I was only able to make the screen so wide, but it looked like all of the colored gif balls I have that act as bullets would all appear on the same line (no CR/LF). On Netscape or IE browsers each dot is the start of a differnt line like a bullet. Not sure why you would not see it. Can anyone else test?

Fixed by changes to CNavDTD.

Fixed in April 5th Build.

Hmmm, not sure what happened, but it looks broken agian....

Fixed (again).

Fixed in the June 4th Build.