Skip to content

Conversation

tabatkins
Copy link
Contributor

@tabatkins tabatkins commented Jul 18, 2025

First commit fixes:

  • A missing </code> on line 936
  • Badly formatted descdef blocks on line 143 and 180
  • Missing 'Repository' metadata, causing the Issue(87) to fail to parse on lines 558 and 592
  • Newly ambiguous autolinks, requiring a few link-defaults entries

The first is a newly-detected bug. The fourth is normal linkrot as the autolinking database grows. The second and third shouldn't have ever worked; I'm confused how compat was building before. I've definitely not done anything recently for them.

With these, the spec builds clean.

Second commit isn't technically necessary, but it removes almost all of the anchors entries, in favor of either using link-defaults when necessary, or in a few places tweaking to use the correct autolink. (Sometimes nothing was necessary; autolinking worked just fine by default.) I've left the CSS3 Images entries, as they are intentionally linking to a very specific draft and need to be preserved as-is.


Preview | Diff

spec:css-conditional-3; type:at-rule; text:@media
spec:css-display-3; type:value; for:display; text:flex
spec:css-flexbox-1; type:value; text:inline-flex
spec:css-syntax-3; type:dfn; text:invalid
spec:filter-effects-1; type:property; text:filter
spec:html; type:element; text:body
spec:infra; type:dfn; text:string
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The new ambiguous string definition is breaking almost all WHATWG specs (and probably others too), so we should probably work to get the source spec updated to stop exporting it instead.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've decided to accept this for now, but I agree that this is a bad state to be in, but mostly for specifications not maintained by the WHATWG as they are not good about addressing warnings and errors.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yup, it's been fixed upstream in Bikeshed. Looks like the spec author actually did the right thing and avoided squatting on the word, but a ReSpec bug caused problems anyway. speced/respec#5007

Copy link
Member

@annevk annevk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@annevk annevk merged commit 1623a6a into whatwg:main Jul 19, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants