- From: Daniel Holbert via GitHub <sysbot+gh@w3.org>
- Date: Thu, 15 Jun 2023 22:42:38 +0000
- To: public-css-archive@w3.org
dholbert has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-anchor-position-1] One of the spec examples has a `anchor-element` mention that's getting interpreted as an HTML element and hence isn't visible == https://drafts.csswg.org/css-anchor-position-1/#example-0b98937b Example 3 has this odd-looking code-comment: ``` // No specified, // so it takes from 'anchor-default'. ``` If you take a look in devtools or in view-source, you can see that it actually says: ``` // No <anchor-element> specified ``` ...and `<anchor-element>` isn't properly escaped, so it gets treated as an unrecognized HTML tag and disappears from the rendered text. I'm not handy enough with BikeShed to know the best incantation to avoid this, but I suspect @tabatkins knows what to do. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8973 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 15 June 2023 22:42:40 UTC