Jan 21 Seamonkey optimized Mac PPC on PBook G3 1. Launch Seamonkey and go to: http://www.zdnet.com 2. Look at column of content titled "Extra" at far right, then compare to 4.51 Communicator. • Extra column should have gray background; it does not. Mac only. win32 shades it in properly. Nested table data. Linux Jan21 build not testable at this time.

Inserting Milestone info.

Setting all current Open/Normal to M4.

Looks like this bug has gone XP and no platform (at least not the current Mac and Win32 builds) will show the Extras frame. Kicking up to Layoutcomponent owner for a looksee.

Well, this is a strange one and I hope it makes more sense to you than it does to me. Here's what happens. For whatever reason, the LAYER element that's used to display the EXTRA positioned element on the far right isn't getting added to the content model. Notice how this is done: <SCRIPT LANGUAGE="JavaScript1.2">if(isIE4){document.write('<SPAN ID="rightArea" style="position:absolute;left:614;top:0;width:165;z-index:100;background-image:u rl(http://www.zdnet.com/zdnn/graphics/heads/rightbackgrnd.gif)">')};</SCRIPT> <LAYER ...> Here's where it gets really interesting. If you load this page from a local file, then it displays correctly. There must be something odd about the way the SCRIPT tag is handled when we load from the net

Hmmm...ZDNet is serving us different content because our user agent string says that we're 5.0. When I changed the user agent to 4.05, we got the correct content and laid out correctly. I'm marking this bug invalid, but I think we're going to need to let content authors know that they need to change their browser sniffing code.

Who is going to relay info to the content authors?

March 19 build, problem seems still exists and manifested in other ways as content has changed...button and fields not positioned properly etc. I looked at source being fed and it looks like their server js app check is feeding IE 3 as last match. We should, if possible, be able to deal with this in more elegant fashion, not just simply say well the content developer has to update their site's js as the only solution. Off hand Vidur do you know what part of the content fed from the server screws us up here? Updated summary to reflect user agent issue rather than the Extras column content which is now no longer present on the site. Reopening for another pass at a better solution.

The problem I saw was not that we were laying stuff out incorrectly, just that we didn't get the column on the right (the one that's in a layer). If there are other layout problems now, they're not mine.

Stop wasting our time with this bug...

Reopening, marking cross platform as problem exists on all OSes, assigning to rickg. If this bug is a duplicate of another known issue please mark it as such. If there is a problem technically with being unable to deal with a particular item of content fed from the server such as the SCRIPT item mentioned, then let's assign this either to be fixed in code to handle user agent 'exceptions' such as this OR assign to a docs person to document and evangelize to content authors the right thing to do.

Chris, re-assigning some of Greg's old bugs to you.

Using the April 4 build of apprunner on Windows NT, this page is nearly unreadable and completely unusable. Input controls are drawn over each other while loading; text is displayed on top of other text; images are scattered around the page, etc. There is something seriously wrong here.

assigning to ekrock

moving to m6

Sent this email to webmaster@zd.com on 6/2/99: Please forward this to the web designer responsible for the http://www.zdnet.com/ home page: Hi, I'm the product manager at Netscape for the Gecko layout engine, and I'm writing to inform you of a bug in your client-side JavaScript client-detection software on the page http://www.zdnet.com/ when viewed using the Nav5 browser (downloadable as milestone build M6 from http://www.mozilla.org/projects/seamonkey/release-notes/index.html ). The bug on the page is that the "gray area" on the right edge of the page does not display under Nav5. The cause of the problem is that your JavaScript client-detection routine here: ---- <SCRIPT LANGUAGE="JavaScript"> <!-- beginRollover = false;// This handles a bug in Nav4.0x that executes the code too quickly. var isNav4, isIE4, isIE3, isNav3; var range = ""; var styleRef = ""; if (navigator.appVersion.charAt(0) >= "4") { if (navigator.appName == "Netscape") { isNav4 = true; layerRef = "document.layers"; styleRef = ""; insideWindowWidth = window.innerWidth; isIE3 = isNav3 = isIE4 = false; } else { isIE4 = true; layerRef = "document.all"; styleRef = ".style"; range = "all."; isIE3 = isNav4 = isNav3 = false; } } else if (navigator.appVersion.charAt(0) < "4") { if (navigator.appName == "Netscape") { isNav3 = true; isIE3 = isNav4 = isIE4 = false; } else { isIE3 = true; isNav3 = isIE4 = isNav4 = false; } } ---- ... does not detect Nav5, so appropriate content is not generated. This can be fixed using our free updated JavaScript client sniffer at http://developer.netscape.com/docs/examples/javascript/browser_type.html ... which detects both Nav5 and IE5. You can view the bug report at http://bugzilla.mozilla.org/show_bug.cgi?id=2550 The full text is pasted below. If you don't have a bugzilla access account, you can sign up for free at http://bugzilla.mozilla.org/ We are eager to see your site fully functional under Nav5 and hope that you will take a moment to update your code to provide full support. Also, as your site is one of those which we test regularly, doing so would assist our QA process and make sure we find any other bugs in Nav5 on your content which might be hidden by this current problem. Please contact me directly if you have any questions. Also, I would greatly appreciate it if you would take a moment to confirm that you've received this message. Thanks very much for your assistance! Sincerely, Eric Krock Senior Product Manager, Netscape Communicator email: ekrock@netscape.com

Have evangelized this; reassigning to M15 for tracking purposes only.

*** Bug 12571 has been marked as a duplicate of this bug. ***

*** Bug 5213 has been marked as a duplicate of this bug. ***

*** Bug 20252 has been marked as a duplicate of this bug. ***

*** Bug 18608 has been marked as a duplicate of this bug. ***

*** Bug 21897 has been marked as a duplicate of this bug. ***

zdnet.com and it's affiliates now render fine. I assume they fixed their useragent bug. It's been working since 1999121608 build on WinNT. I assume it's fixed for Mac now too, but I can't verify that, so I won't mark this as worksforme.

ZDNet has been notified and is upgrading their page to a new look that will be fine under M12. INVALID. LAYER, ILAYER, document.layers[] not supported in Gecko/Nav5. Closed.

*** Bug 3996 has been marked as a duplicate of this bug. ***

Okay.

ZDnet pages are rendered differently in Netscape 4.72 and Mozilla 5.0 (2000032109 build for Linux). What have to be rendered side by side are not rendered that way in Mozilla 5.0 while they are in Netscape 4.72. Their Java script client detection routine regards Mozilla 5.0 as MS IE 4.0 and I'm sure their pages are rendered as intended by the author in MS IE 4.0(though I didn't check) so that something could be wrong in Mozilla 5.0.

*** Bug 3996 has been marked as a duplicate of this bug. ***