Closed
Bug 50940
Opened 24 years ago
Closed 24 years ago
In QuirksMode, %-width is not calculated compatibly
Categories
(Core :: Layout, defect, P3)
Core
Layout
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: attinasi, Assigned: ian)
Details
(Keywords: compat, css3, relnote, Whiteboard: easy fix)
Mozilla calculates %-width values according to the CSS2 spec. This is great for
strict mode documents, but in quirks mode Mozilla should emulate Nav and IE,
which calculate %-widths differently.
The markup:
<html>
<body>
<div style="border: 1px solid green; background: white; width:90%">
Outer Div
<div style="margin: 2em; border: 1px solid red; background: gray;
width:100%">
Inner Div
</div>
</div>
</body>
</html>
In Nav and IE the inner div is contained within the outer div (the 100% width is
calculated such that the margin and border are included in the total width)
whereas in Mozilla it extends outside the outer div. In Quirks Mode we should
look like Nav and IE (possibly use box-sizing: border-box; liberally in
quirk.css?)
Assignee | ||
Comment 1•24 years ago
|
||
If we want to fix this, it is easy to do it in quirk.css.
However, I think that this would cause authors major problems when doing their
transition to the standards.
Release note item:
Mozilla supports the 'width' CSS property according to the W3C
recommendations, and thus is not fully compatible with legacy browsers
such as Microsoft Internet Explorer for Microsoft Windows. It is
possible to make Mozilla use a compatible definition for 'width' by
inserting the following line in any stylesheets used:
* { box-sizing: border-box; }
That property should probably be renamed, since the draft has already started
changing its exact semantics/values...
WONTFIX?
See also bug 50449.
Comment 3•24 years ago
|
||
>and thus is not fully compatible with legacy browsers such as Microsoft
>Internet Explorer for Microsoft Windows
Even if Internet Explorer was completely standards compliant, we wouldn't be
trying to make Mozilla compatible with MSIE. Some effort might go toward
things like bug 6211 (hi again Ian!) that's currently spent on quirkiness.
Also, it doesn't seem quite right to call MSIE a "legacy browser", especially
without giving a version number or range of version numbers.
Assignee | ||
Comment 4•24 years ago
|
||
Jesse: I think you misunderstood. That quote was what I would suggest as a
release note item.
I'm not going to 'fix' this. 'Fixing' this would cause more trouble on the long
run than leaving it as currently, IMHO. Microsoft should fix their bugs, and
that's that.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → WONTFIX
Comment 5•24 years ago
|
||
I was trying to suggest that the release note be reworded. It sounds like
you're saying msie and ns6 would be completely compatible if msie was compliant
with certain standards. Also, I don't think it's appropriate to call a
competitor's product a "legacy browser", especially without giving version
numbers.
Assignee | ||
Comment 6•24 years ago
|
||
> It sounds like you're saying msie and ns6 would be completely compatible if
> msie was compliant with certain standards.
That's exactly what I'm saying. It's the whole point of standards.
Here is a new release note item:
Mozilla supports the 'width' CSS property according to the W3C
recommendations, and thus is not fully compatible with legacy browsers such
as Microsoft Internet Explorer 5.5 for Microsoft Windows. It is possible to
make Mozilla use a definition for 'width' compatible with IE by inserting
the following line in any of the stylesheets used:
* { -moz-box-sizing: border-box; }
Any better?
You need to log in
before you can comment on or make changes to this bug.
Description
•