[cssom][css-grid][css-transforms] Make 'transform-origin' and 'perspe…

[zcorpan]

…ctive-origin' resolved value like 'height'

Fixes #392.

[mrego]

Just one question, shouldn't grid-row-gap and grid-column-gap be marked too?
https://drafts.csswg.org/css-grid/#propdef-grid-column-gap

And one nit, the commit says css-grid but doesn't talk about grid properties. Probably it'd be nice to update the commit title and description.

[zcorpan]

Just one question, shouldn't grid-row-gap and grid-column-gap be marked too?
https://drafts.csswg.org/css-grid/#propdef-grid-column-gap

No, the spec for those doesn't say anything about "resolved value", so they work like normal properties. (If implementations disagree, please file a new issue.)

And one nit, the commit says css-grid but doesn't talk about grid properties. Probably it'd be nice to update the commit title and description.

OK, yeah.

Thanks!

[zcorpan]

Proposed commit message when merging

[cssom][css-grid][css-transforms] Make 'transform-origin' and 'perspective-origin' resolved value like 'height'

Also mention that 'grid-template-rows' and 'grid-template-columns'
are resolved value special case properties (no normative change).

Fixes #392.

[mrego]

Just one question, shouldn't grid-row-gap and grid-column-gap be marked too?
https://drafts.csswg.org/css-grid/#propdef-grid-column-gap

No, the spec for those doesn't say anything about "resolved value", so they work like normal properties. (If implementations disagree, please file a new issue.)

Yes sorry for the noise, I was mixing in my mind again computed vs resolved value.

[fantasai]

Looks OK to me.