height/width computed value not inherited when max/min applied

RESOLVED INVALID

Status

()

P3
normal
RESOLVED INVALID
17 years ago
11 years ago

People

(Reporter: fantasai.bugs, Assigned: dbaron)

Tracking

({css2, testcase})

Trunk
Future
css2, testcase
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [Hixie-P3])

Attachments

(1 attachment)

(Reporter)

Description

17 years ago
Overview:

	According to CSS2, the max-width and min-width properties influence the
	computed width of an element's box. Likewise for max-height and
	min-height. Mozilla just inherits the value of width/height.

	http://www.w3.org/TR/REC-CSS2/visudet.html#min-max-widths
	http://www.w3.org/TR/REC-CSS2/visudet.html#min-max-widths

Steps to Reproduce:

	Open up testcase in Mozilla

Actual Results:

	Except for the the test with auto width + max-width, the inherited
	values of width and height are the specified values, not computed
	values.

Expected Results:

	Each inner <div> should have the same width/height as its parent.

Tested on Mozilla nightly build (id: 2001080203) on Windows 2000

Additional Comments:

	I thought perhaps Mozilla inherited the parent <div>s width before
	applying max-width/min-width, but if this were the case, the auto
	width test's inner <div> would fill the width of the body.
(Reporter)

Comment 1

17 years ago
Created attachment 44766 [details]
testcase
(Reporter)

Updated

17 years ago
Keywords: css2, testcase
Whiteboard: [Hixie-P3]

Updated

17 years ago
Status: NEW → ASSIGNED
Priority: -- → P3
Target Milestone: --- → mozilla1.0

Updated

17 years ago
Target Milestone: mozilla1.0 → mozilla1.1
Bulk moving from Moz1.1 to future-P1. I will pull from this list when scheduling
work post Mozilla1.0.
Priority: P3 → P1
Target Milestone: mozilla1.1 → Future

Comment 3

17 years ago
cc'ing myself
Assigning pierre's remaining Style System-related bugs to myself.
Assignee: pierre → dbaron
Status: ASSIGNED → NEW
Priority: P1 → P3
The definition of computed value has been changed in CSS 2.1, so this is now
invalid.
Status: NEW → RESOLVED
Last Resolved: 15 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.