http://members.xoom.com/rootrider/index.html contains a table with a single row and seven TD's that is used as a common navigation menu for each of my pages on this site. The very first time I viewed this page in the Developer Preview downloaded from developer.netscape.com on 1/30/99, the table rendered perfectly. But after I scrolled down to the bottom of the page and then clicked "go to the top", the table rendered only the first four table cells correctly, with the fifth cell rendered half in and half out of the main table "constraints". I then reloaded the page, type the URL in manually, etc. but it the problem was still displayed. (That's it...) -Joel D. Parker

Also, I'm viewing the site in the Developer Preview (Gecko) downloaded from http://developer.netscape.com on 1/30/99. -Joel D. Parker

The bug described is the '<table width=nn%>' type of bug that is (apparently) only seen on Windows for optimized builds. The good news is that the Jan 29th build (Win95) appears to have fixed this problem (whereas it was visible in every build up to and including Jan 28th).

The bug described is the '<table width=nn%>' type of bug that is (apparently) only seen on Windows for optimized builds. In cases with 'table width=nn%' and an IMG in the right-most TD, the image sometimes seems to not appear. (I've also noticed this on my.netscape.com, for example). If you do a resize (reflow), the image "appears". However, the good news is that the Jan 29th build (Win95) appears to have fixed this problem (whereas it was visible in every build up to and including Jan 28th).

Oops. Above entry applies to #2823. Sorry.

Setting all current Open Critical and Major to M3

per leger, assigning QA contacts to all open bugs without QA contacts according to list at http://bugzilla.mozilla.org/describecomponents.cgi?product=Browser

I can't seem to load this page either in 4.5 or the viewer. In 4.5 I get a network error and in the viewer it never loads and gives a bunch of javascript errors in the process.

Chris, I'm working on M3 bugs and won't be able to look at this immediately. It would help if you could put the JavaScript errors in the bug report.

The javascript error is just a symptom of a blank document. The parser is placing the body ahead of the frameset in the content model and the page appears blank, because in a frameset document, the frameset must come first. Rick: I've seen this problem before but can't remember the bug numbers. When it gets fixed, please check to see if the original problem still exists. I tried just loading the problem document (http://members.xoom.com/rootrider/_XOOM/rootrider/index.html) but it did not exhibit the bad behavior that was reported. JavaScript error: top.thePage has no properties URL :http://members.xoom.com/rootrider/index.html, LineNo :19 Line text: '(null)', Error text: '(null)'

Sorry that the page is inaccessible. XOOM introduced the "XOOMbar" yesterday which essentially inserts an ad frame into each page. Since it just came out yesterday (3/15/99), there seem to be quite a few bugs. I couldn't access my site in both IE4 and Navigator 4.05 or 4.51. I have found, though, that if you type in the complete address, with _XOOM inserted in the middle, the page works fine. (ie: http://members.xoom.com/_XOOM/rootrider/index.html) Try it now. -Joel D. Parker

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

Checked in a fix yesterday ( Mar 17). Should be able to view the page without any problems. Marking the bug fixed.

Fixed in big script update.

Using 3/22 build on Win 95, Win NT, Win 98, Mac85. and Linux, verifying bug fixed in terms of the table rendering. However, there is another problem. If you load the page, scroll down and click on the link back to http://members.xoom.com/rootrider/index.html, the 1st frame is rewritten on top of the last. If you keep clicking, the 1st fram will multiply. Will look into this further on Tuesday.

To tell you truth, I haven't looked into this problem personally, but you might also consider the fact that XOOM has implemented their ad system recently, so this *may* be causing or helping the problem. -Joel D. Parker