many computed values are incorrect - by the_dees

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

ID 559441 Comments
Status Closed Workarounds
Type Bug Repros 1
Opened 5/16/2010 6:17:03 AM
Duplicates 586402 Access Restriction Public


The computed value of a property is often incorrect. That is if a computed value is dependent on another property, that other property is ignored. This can be tested using the inherit keyword.

Public testcase:

This bug was previously reported a few times, see
ID#344787 (Inherited margin with inherit keyword: the computed value's parent should be inherited),
ID#429559 (TH element does not inherit text-align),
ID#469093 ('border-color' of ascendant isn't inherited (using 'border-color:inherit') when that element has a 'color' value defined).

The problem is not local to the properties mention but global, i.e. it applies to any property.
Sign in to post a comment.
Posted by the_dees on 2/25/2014 at 5:58 AM
Yes, this issue has been fixed. Thanks.
Posted by Microsoft on 3/1/2012 at 10:03 AM

Thank you for your feedback.

This issue was resolved in Internet Explorer 10 on Windows 8 Consumer Preview released on 2/29/2012. You can download the Consumer Preview from here: Please verify the changes and file a new feedback or reactivate the existing one if the problem persists.

Best regards,

The Internet Explorer Team

Posted by the_dees on 6/7/2011 at 9:34 AM
Please note that no other browser has this issue. All correctly inherit computed values.

Also note that in a recent discussion on the www-style mailing list, it was cleared that computed values are inherited, not specified ones as IE does. See
Posted by the_dees on 6/3/2011 at 5:23 AM
I have one question:

Since there are a lot of properties affected by this issue, should I report each property separately or would it be ok to write one big test case with a section for each property?
Posted by the_dees on 5/1/2011 at 6:17 AM
inherit should really be fixed completely in IE10. It is an basic and important concept in CSS.
Posted by Microsoft on 4/7/2011 at 11:22 AM
Thank you again for your feedback.

We were able to validate your feedback. However, based on the limited impact this bug may have, we will not be able to address this bug during this release.

Your feedback is very important to us, and it helps us improve the quality of Internet Explorer. We continue to welcome more feedback, so please don't hesitate to report other ways that we can improve Internet Explorer.

Best regards,

The Internet Explorer Team
Posted by the_dees on 8/14/2010 at 11:07 AM
Thanks for your message.

Please not that the third issue is not only an issue for the margin and padding property, but for all properties listed below.

That means, given this pseudo code:
.parent { property: value; }
.child { font-size: 2em; property: optional-reset; property: inherit; }
<div class="parent">Line 1.<div class="child">Line 2.</div></div>

property: One of the properties listed below.
value: A value that contains em lengths.
optional-reset: If property is inherited, this property:value declaration is used to prevent inheritance, so the inherit keyword has to be explicitly used.

Given the code above, these properties have their computed/inherited values incorrectly calculated:

background-position (even if it's part of the background shorthand)
border, border-width, border-top, border-right, border-bottom, border-left, border-top-width, border-right-width, border-bottom-width, border-left-width
bottom, left, right, top
clip [rect()]
height, width
max-height, min-height
max-width, min-width
letter-spacing, word-spacing
margin, margin-top, margin-right, margin-bottom, margin-left
outline, outline-width
padding, padding-top, padding-right, padding-bottom, padding-left

It seems only the font, font-size and line-height properties are not affected by this bug.
Posted by Microsoft on 8/13/2010 at 6:04 PM

Thank you for your blog post. Looks like the original acknowledgement post a few months ago didn't make it somehow.

As you are aware, the first two issues have been resolved. We are have been investigating the third issue and will let you know when we have a resolution.

Since this issue has multiple issues, we'll let the resolution of the third issue decide the resolution status of this feedback.

Best regards,

The Internet Explorer Team
Posted by the_dees on 8/5/2010 at 10:44 AM
As of Preview #4, the first and the second paragraph work correctly.

However, the graphical tests still fail. Likely a lot of properties are not yet fixed when it comes to their computed values.

I'd like to know you're aware of this issue. It is one of the bigger missings in IE's CSS implementation.
Posted by the_dees on 6/24/2010 at 6:15 AM
The second paragraph in the testcase now works correctly.

I understand that this reporte is a bit too generic, but I'd like to know whether the issue is know and/or worked on. Thanks.