Closed Bug 3454 Opened 26 years ago Closed 25 years ago

ignoring scrollbars when sizing tables

Categories

(Core :: Layout, defect, P2)

Product:
Core
Component:
Layout
Platform:
x86
Windows 95
Type:
defect

Tracking

()

Status:
VERIFIED FIXED

People

(Reporter: dbaron, Assigned: karnaze)

References

(
URL
)

Details

You seem to have started ignoring scrollbars when sizing tables.  There should
be no horizontal scrollbar on the above URL, and each table should have the
same margin on each side (See bug #3000 for other problems on this page).

This problem started between builds 1999-03-02 and 1999-03-05 (Win95, optimized
builds)
Status: NEW → ASSIGNED
This small example reproduces the problem. Note that if you remove the "margin:
1em", then it displays correctly

<html><head>
<style type="text/css">
TABLE	{ margin: 1em; width: auto; }
</style>
</head>
<body>

<table class="two">
 <tr>
  <th>Header One</th>
  <th>Header Two</th>
  <th>Header Three</th>
 </tr>
 <tr>
  <td>
   This table uses the separated borders model.
  </td>
  <td>
   This means that elements within the cell have border-spacing of 1em.
  </td>
  <td>
   The borders on the header cells,
   on all sides, should be medium solid purple.
  </td>
 </tr>
</table>

</body></html>
Target Milestone: M6
Target Milestone: M6 → M7
QA Contact: 4144 → 4110
Target Milestone: M7 → M9
troy returns soon. -> m9
dbaron, is the workaround all we need?
Target Milestone: M9 → M11
Target Milestone: M11 → M13
Assignee: troy → karnaze
Status: ASSIGNED → NEW
Chris, this is the same kind of bug you mentioned in the email. It sounds like
you're working on it so I'm reassigning this to you.

I just remembered another detail about this problem. Currently, the 'available
width' in the reflow state isn't correct when it comes to margins. We define it
that the available width is the amount of space available for the frame's
bounds.

The frame's bounds do not include it's margin, so the available width should be
reflect that. Instead, the way it is today the available width includes the
margin area and that's why tables are having a problem.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
This was fixed a day or two ago.
Status: RESOLVED → VERIFIED
Using the small sample with the 10/20 app, bug appears to be fixed. Verifying as
so.
You need to log in before you can comment on or make changes to this bug.