225206 2021-04-29 13:26:23 -0700 CSS shorthand should serialize as empty string when longhands have variables 2022-07-28 15:01:01 -0700 1 1 1 Unclassified WebKit CSS WebKit Nightly Build Unspecified Unspecified RESOLVED DUPLICATE 230389 https://bugs.chromium.org/p/chromium/issues/detail?id=616341 BrowserCompat, InRadar P2 Normal --- 1 obrufau webkit-unassigned justin koivisto simon.fraser webkit-bug-importer oldest_to_newest 1755514 0 obrufau 2021-04-29 13:26:23 -0700 Run this code: ```js document.body.style.cssText = ` --t: 1px 2px; --r: 3px; --b: 4px; --l: ; margin-top: var(--t); margin-right: var(--r); margin-bottom: var(--b); margin-left: var(--l); `; getComputedStyle(document.body).margin; // "0px 3px 4px 0px" document.body.style.margin; // BAD: "var(--t) var(--r) var(--b) var(--l)" document.body.style.margin += ""; getComputedStyle(document.body).margin; // "1px 2px 3px 4px" ``` The margin shorthand shouldn't be serialized concatenating the var() notations, because that can have a different meaning! It should be serialized as empty string instead. The specs are not much clear about this (https://github.com/w3c/csswg-drafts/issues/6253), but Chromium and Firefox do the reasonable thing and serialize as empty string. 1757601 1 webkit-bug-importer 2021-05-06 13:27:13 -0700 <rdar://problem/77622517> 1781759 2 obrufau 2021-08-03 15:20:56 -0700 Chromium was fixed in https://crbug.com/616341 1793697 3 justin 2021-09-15 07:26:20 -0700 Another example of reproducing this bug: https://jsfiddle.net/9gft8hkr/5/ (from: https://bugs.chromium.org/p/chromium/issues/detail?id=1218159#c12) 1793712 4 obrufau 2021-09-15 08:33:54 -0700 No, your expectations in https://jsfiddle.net/9gft8hkr/5/ are wrong. Chromium and Firefox are correct. WebKit is wrong but it's unrelated to this issue, it's bug 225209 and something else. 1887461 5 obrufau 2022-07-28 15:01:01 -0700 This was fixed as part of bug 230389. Kinda strange that this seems to only have a test in css-logical, nothing in css-variables or cssom, but oh well. *** This bug has been marked as a duplicate of bug 230389 ***