- From: Daniel Holbert via GitHub <sysbot+gh@w3.org>
- Date: Mon, 09 Jan 2017 18:46:19 +0000
- To: public-css-archive@w3.org
dholbert has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-content] `none` and `normal` values (for `content` property) are never linkified == In the css-content spec, the `none` and `normal` values (for the `content` property) are never linkified, but probably should be. I suspect there's some bug in the markup that prevents the correct link target from being inferred/discovered when bikeshed is generating HTML. Other values of the same property (like e.g. the `contents` value) *are* successfully linkified. Sample sections of the spec where this is noticeable: * In the definition of the `normal` value, two other values are mentioned -- `contents` and `none`. The former is linkified, the latter is not. https://drafts.csswg.org/css-content/#normal * In the definition of the `contents` value, all three values (`none`, `normal` and `contents`) are mentioned. Again, only `contents` is linkified. https://drafts.csswg.org/css-content/#valdef-content-contents I don't know bikeshed markup very well, but I'm guessing that perhaps the issue is that there's no `dfn-for="content"` attribute, on the `<dl>` parent of the none & normal `<dfn>` tags...? (At least, the correctly-working `contents` value does have a `dfn-for` attribute on its `<dl>` parent in the bikeshed markup.) CC @tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/874 using your GitHub account
Received on Monday, 9 January 2017 18:46:29 UTC