Closed Bug 1517 Opened 26 years ago Closed 26 years ago

{compat} minimum width of floating elements

Categories

(Core :: Layout, defect, P5)

x86
Windows 95
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: howcome, Assigned: buster)

References

()

Details

(Whiteboard: Requested additional info from assigned engineer prior to verification)

Section (12) of the test page show a floating element where the width has ben set to be very small. In such cases, the UA is allowed to increase the value. From section 4.1.2 of CSS1: "The 'width' has a non-negative UA-defined minimum value (which may vary from element to element and even depend on other properties). If 'width' goes below this limit, either because it was set explicitly, or because it was 'auto' and the rules below would make it too small, the value will be replaced with the minimum value instead." Current thinking goes towards interpreting the above quite liberally, i.e. let the UA use whatever value it finds the best.
Assignee: peterl → troy
Component: Style System → Layout
Assignee: troy → kipp
We talked about this, and I think you may already be doing it
Severity: enhancement → normal
Status: NEW → ASSIGNED
Severity: normal → major
Priority: P2 → P5
Summary: minimum width of floating elements → {compat} minimum width of floating elements
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
Fixed. We now apply a minimum width to objects that have a specific width setting that is "too small".
Whiteboard: Requested additional info from assigned engineer prior to verification
Kipp, what is the minimum width for objects that have a specific width setting that is "too small"? I could not find that addressed in the ua.css file for the 3/26 build. I'm not sure where else to look.
Status: RESOLVED → VERIFIED
The minimum width is undefined, and outside the spec. The value used is the "natural" minimum width when the object is reflowed with a zero available width, which means that each line will be as short as possible. As that varies from content to content, there is no easy answer.
You need to log in before you can comment on or make changes to this bug.