We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The syntax of the string-set property is defined as follows:
string-set
none | [ <custom-ident> <string>+ ]#
However, lots of the examples in the spec seem to use a different syntax:
head > title { string-set: title contents; }
H1 { string-set: chapter contents; }
h2 { string-set: heading content() }
h1 { string-set: header content(before) ':' content(text); }
The problem seems that before dc01554, the syntax was
[[ <custom-ident> <content-list>] [, <custom-ident> <content-list>]* ] | none
In Named strings, the spec still says
The string-set property accepts values similar to the content property, including the extraction of the current value of counters.
content
But unlike attr(), defined in CSS Values, I don't think <content-list> is allowed wherever a <string> is expected.
attr()
<content-list>
<string>
The text was updated successfully, but these errors were encountered:
No branches or pull requests
The syntax of the
string-set
property is defined as follows:However, lots of the examples in the spec seem to use a different syntax:
head > title { string-set: title contents; }
H1 { string-set: chapter contents; }
h2 { string-set: heading content() }
h1 { string-set: header content(before) ':' content(text); }
The problem seems that before dc01554, the syntax was
In Named strings, the spec still says
But unlike
attr()
, defined in CSS Values, I don't think<content-list>
is allowed wherever a<string>
is expected.The text was updated successfully, but these errors were encountered: