15384 2012-01-02 13:06:03 +0000 Value assignment on shorthand properties is not well-defined 2013-08-08 13:26:37 +0000 1 1 1 Unclassified CSS CSSOM unspecified All All RESOLVED FIXED P2 normal --- 1 antonsforums zcorpan glenn kennyluck zcorpan public-css-bugzilla oldest_to_newest 62194 0 antonsforums 2012-01-02 13:06:03 +0000 Reported by Øyvind Stenhaug Value assignment on shorthand properties is not well-defined. For example, some combinations of longhand property values cannot be represented by a value on the corresponding shorthand property: What is the computed value of 'border' given the following computed values of longhand properties? border-top-style: solid border-right-style: none border-bottom-style: none border-left-style: none Conversation begins: http://lists.w3.org/Archives/Public/www-style/2011Oct/0473.html Bug description: http://lists.w3.org/Archives/Public/www-style/2011Oct/0476.html 62195 1 antonsforums 2012-01-02 13:09:13 +0000 Gecko apparently doesn't handle getPropertyValue on computed style for shorthand properties in an ideal manner (cf https://bugzilla.mozilla.org/show_bug.cgi?id=137688 , http://stackoverflow.com/questions/4230022/get-border-value-with-getcomputedstyle-getpropertyvalue-mozilla-ff ) which may be as a result of this issue. 62196 2 antonsforums 2012-01-02 13:13:58 +0000 Related: some implementers think that shorthands should "just work" so that there's no noticeable affect if a property changes from being a longhand to a shorthand property, unless the value specified is one that can't be specified in the original (now shorthand) form. (eg: http://lists.w3.org/Archives/Public/www-style/2010Feb/0104.html ) That does doesn't solve the hard case described, though. 62216 3 antonsforums 2012-01-02 22:49:14 +0000 Bug 15387 is another example of this bug. 90000 4 zcorpan 2013-06-28 13:44:44 +0000 https://dvcs.w3.org/hg/csswg/rev/29e1b40f9bb1 https://dvcs.w3.org/hg/csswg/rev/a45add1017ef