We should add "<string>" as a valid syntax for custom property registration:
https://www.w3.org/TR/css-properties-values-api-1/#supported-names
Chrome got a bug report that "<string>" was expected to work for registered custom properties to be used in the content property.
We should add
"<string>"as a valid syntax for custom property registration:https://www.w3.org/TR/css-properties-values-api-1/#supported-names
Chrome got a bug report that
"<string>"was expected to work for registered custom properties to be used in the content property.