false
432
plain_text
<p>This is an undocumented bug, but apparently quite common. Netscape is creating a carriage return in the middle of your code. It happens randomly and the only fix is to use space characters within the HTML to compensate the carriage return.
<br />On 17:32:57 18 January 2001 dollars wrote:
<br />>Have any of you encountered this Netscape bug? We've
<br />>built a streaming media site for 4.0 browsers and above
<br />>that uses a Java backend. For some reason when viewing
<br />>the site in Netscape the NS browser puts random breaks in
<br />>the code that we call whitespace bugs. Depending on where
<br />>it happens it can have either no effect on the page or it
<br />>can happen right in the middle of a tag which then cause
<br />>the page to be thrown all out of whack. Sometimes the
<br />>break happens before the closing of a tag which then
<br />>causes the tag to appear as text on the page.
<br />>
<br />>It's weird because we have some really solid programmers
<br />>and we know of one other company that's encountered the
<br />>same bugs. We thought it might relate to our server setup
<br />>but this other company's site uses different technology.
<br />>
<br />>Any insight into solving this problem would be greatly
<br />>appreciated.</p>
This is an undocumented bug, but apparently quite common. Netscape is creating a carriage return in the middle of your code. It happens randomly and the only fix is to use space characters within the HTML to compensate the carriage return.
On 17:32:57 18 January 2001 dollars wrote:
>Have any of you encountered this Netscape bug? We've
>built a streaming media site for 4.0 browsers and above
>that uses a Java backend. For some reason when viewing
>the site in Netscape the NS browser puts random breaks in
>the code that we call whitespace bugs. Depending on where
>it happens it can have either no effect on the page or it
>can happen right in the middle of a tag which then cause
>the page to be thrown all out of whack. Sometimes the
>break happens before the closing of a tag which then
>causes the tag to appear as text on the page.
>
>It's weird because we have some really solid programmers
>and we know of one other company that's encountered the
>same bugs. We thought it might relate to our server setup
>but this other company's site uses different technology.
>
>Any insight into solving this problem would be greatly
>appreciated.
2001-01-25T09:15:52+00:00
true
147
250
448
2001-01-25T09:15:52+00:00