Re: [svgwg] What should the computed value of the `marker` shorthand property be when its longhands have different values (#983)

Oh, I didn't know that rule! 

Looking at CSSOM, I think my reading of it means that for `marker`, the computed value would always be the empty string, since:

1. In https://www.w3.org/TR/cssom-1/#dom-cssstyledeclaration-getpropertyvalue, you would create a list of the 3 marker longhands.
2. Then, in https://www.w3.org/TR/cssom-1/#serialize-a-css-value, you would apply rules 1.1 and 1.2:

> 1.1 Let shorthand be the first shorthand property, in [preferred order](https://www.w3.org/TR/cssom-1/#concept-shorthands-preferred-order), that exactly maps to all of the longhand properties in list.
> 1.2 If there is no such shorthand or shorthand cannot exactly represent the values of all the properties in list, return the empty string.

Although maybe I am misunderstanding what "maps to all of the longhand properties in list" means?

Are there any other examples of places where the computed value of a shorthand would be the empty string?

-- 
GitHub Notification of comment by weinig
Please view or discuss this issue at https://github.com/w3c/svgwg/issues/983#issuecomment-3000564926 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 24 June 2025 13:45:51 UTC