If you look at this test:
|
test_valid_value('transition', 'allow-discrete display', 'display 0s ease 0s allow-discrete'); |
You'll notice that it is expected that the transition shorthand serializes all longhand values, including those set to initial values. I was under the impression, although I don't have spec references handy, that serialization of shorthand would always try to yield the shortest value.
Interestingly, the new transition-behavior property seems to not follow the same rule, for instance:
|
test_valid_value('transition', |
|
'normal opacity, color, allow-discrete display', |
|
'opacity 0s ease 0s, color 0s ease 0s, display 0s ease 0s allow-discrete'); |
Notice here that transition-behavior is only serialized in the transition shorthand when the non-initial value allow-discrete is specified.
What are the specs mandating this?
If you look at this test:
wpt/css/css-transitions/parsing/transition-behavior.html
Line 16 in c0ee967
You'll notice that it is expected that the
transitionshorthand serializes all longhand values, including those set to initial values. I was under the impression, although I don't have spec references handy, that serialization of shorthand would always try to yield the shortest value.Interestingly, the new
transition-behaviorproperty seems to not follow the same rule, for instance:wpt/css/css-transitions/parsing/transition-behavior.html
Lines 51 to 53 in c0ee967
Notice here that
transition-behavioris only serialized in thetransitionshorthand when the non-initial valueallow-discreteis specified.What are the specs mandating this?