For further information about email marketing, download Econsultancy's Email Census (based on a survey of digital marketers) and the Email Marketing Platforms Buyer's Guide (particularly relevant for the UK market). See also the Email Statistics Compendium.
online magazine vs integrated content 9 replies Looking For CRM Vendor/Software 4 replies Mega Menu's and SEO 4 replies PPC Benchmarks for Catalog/Online Apparel e-Tailers 1 reply Finding an appropriate affiliate network 2 replies
Homepage vs Landing Page 761 views Best practice approach to securing user engagement with a company intranet 609 views Donovan iDesk or Mediabank Interactive mediaplanning tools 564 views Email marketing 537 views Building a bespoke PDF brochure via web form 501 views
Best practice approach to securing user engagement with a company intranet 7 replies Email marketing 5 replies Query: Which agency designed this? 5 replies Building a bespoke PDF brochure via web form 4 replies Email Marketing 4 replies
Producer at Alltrue.com
18 January 2001 17:32pm
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.
CEO at Econsultancy
19 January 2001 10:37am
Pesky Netscape.... What build version of Netscape 4 are you getting these errors with? 4.01? 4.05? 4.08? 4.5 etc? Look in Help > About Navigator
Producer at Alltrue.com
19 January 2001 14:26pm
It's in all Netscapes above 4.08, Mac and PC. It's not your normal cross browser cross platform bug. I know it sounds fishy like it's got to be something we're doing wrong but I just heard of another project with different programmers that had the same problem. We can't tell if Netscapes don't like our use of frames, or maybe our stylesheets. I'll check the Help section to see if it mentions anything.
Producer at Alltrue.com
19 January 2001 14:42pm
When I read "look in Help" I was thinking you had a Help section about browsers quirks and workarounds. Believe me I wish finding the browser version was a problem but unfortunately my issue is a lot bigger than that.
CEO at Econsultancy
19 January 2001 14:59pm
Sorry - the look in 'Help' bit was just to find out the build version not get the answer unfortunately. I'll ask around and see if anyone has encountered and solved this...
We've had problems with earlier builds of Netscape 4 (hence my question) but 4.08 should be OK.
Group Manager at Infosys
25 January 2001 09:15am
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.