issue-link js-issue-link" data-error-text="Failed to load title" data-id="2004817243" data-permission-text="Title is private" data-url="https://github.com/w3c/browser-specs/issues/1135" data-hovercard-type="pull_request" data-hovercard-url="/w3c/browser-specs/pull/1135/hovercard" href="https://github.com/w3c/browser-specs/pull/1135">#1135 actually had a couple of issues that made the code essentially useless because it only ran on a handful of IETF specs: - the code favored info from Specref over info from IETF - the code only really applied to drafts due to a buggy RegExp Fixing these problems yielded a new issue: the assumption that HTTP WG specs are always available under `httpwg.org` turns out to be wrong. Also, there are other specs that are not published by the HTTP WG but that still have an `httpwg.org` version. The code now looks at the actual list of specs in the underlying GitHub repository: https://github.com/httpwg/httpwg.github.io. As a result, the nightly URL of all IETF specs that have an `httpwg.org` version now targets that version, implementing the suggestion in #933 (see that issue for the list of affected specs). A companion PR was sent to Specref to implement a similar switch there: tobie/specref#766 The code also looks at the obsolescence data in datatracker and sets the `standing` and `obsoletedBy` properties accordingly. This fixes #327.

Commits

Commits on Nov 23, 2023

Fix and improve processing of IETF specs