You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
And referenced in the Table of Contents via target-text:
#contents ul li a::before { content: target-text(attr(href)); }
Note that the input text is normal mixed case:
<li><a class=h1 href="#Introduction"></a></li>
<h1 id="Introduction">Introduction</h1>
However the target-text in the ToC ends up being uppercased, as opposed being mixed case. I'm not sure whether this is intended (poor spec again) or accidental (i.e. a bug). Practically it would make sense for target-text to retrieve the original untransformed text, so text-transform can be applied independantly (or NOT).
The text was updated successfully, but these errors were encountered:
In this example:
target-text-attr-bug.zip
The headers are uppercased through CSS:
h1 { text-transform: uppercase; break-before: page; }
And referenced in the Table of Contents via target-text:
#contents ul li a::before { content: target-text(attr(href)); }
Note that the input text is normal mixed case:
<li><a class=h1 href="#Introduction"></a></li>
<h1 id="Introduction">Introduction</h1>
However the target-text in the ToC ends up being uppercased, as opposed being mixed case. I'm not sure whether this is intended (poor spec again) or accidental (i.e. a bug). Practically it would make sense for target-text to retrieve the original untransformed text, so text-transform can be applied independantly (or NOT).
The text was updated successfully, but these errors were encountered: