Closed Bug 2207 Opened 26 years ago Closed 25 years ago

The above website does not display properly

Categories

(Core :: Layout, defect, P2)

x86
Windows 95
defect

Tracking

()

VERIFIED WORKSFORME

People

(Reporter: wstudio, Assigned: karnaze)

References

()

Details

At times the above URL does not display fully or does not display at all.
(tested on Nightly Jan 5 non-debug build Win 95) Just a couple of comments: This
page is a frameset with a left and a right frame with 'cols="187,*"'.

A) The _right_ hand frame has three problems: 1) missing image of right
   'bookend' near top, 2) missing third column of table midway down, and 3) 'not
   100% width' black table near bottom. If you force a reflow, then everything
   is fine.

   All three of these flaws are tied to the "<table width='nn%'>" (#1474 and
   others). This problem can also be seen at 'resource:/res/samples/test3.html'.

   [Test: If you nuke the width="100%" attributes of the tables, then the right
   'bookend' and the third column show up on loading (albeit with tables not
   necessarily at 100% width).]

B) The _left_ hand frame, when fully maximized, has a 'scrollbar-width' white
   space on the right and bottom edges (on my build/box). This sounds similar to
   #2216 which was just filed (but I can't see it; it is on an internal server).
Assignee: blythe → rickg
Component: Windows FE → Layout
Product: Mozilla → NGLayout
Reassigning blythe to rickg and changing component to nglayout.
Assignee: rickg → karnaze
The only problem I could confirm is the table width issue. Please look.
Status: NEW → ASSIGNED
Setting all current Open/Normal to M4.
per leger, assigning QA contacts to all open bugs without QA contacts according
to list at http://bugzilla.mozilla.org/describecomponents.cgi?product=Browser
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
Target Milestone: M4 → M5
It looks ok on 3/29 optimized WinNT. Chris P, please verify on Win95.
Status: RESOLVED → VERIFIED
Looks fine in Win 95 with April 5th Build.
You need to log in before you can comment on or make changes to this bug.