Denis Ah-Kang

Expose specification's tags

3

Would be useful.

`requirements` should be use to list the restrictions on the parameters. If there's a path parameter like `api/reports/{report}`, `{report}` should be listed in the parameters. It brings another problem which...

fixup.js has now various purposes (ToC handler, outdated warning, analytics). I would be good to separate these scripts and repackage fixup.js from these scripts. c.f. https://github.com/w3c/tr-design/pull/229

set minimum heigh for TOC items (WCAG 2.2 success criterion)

1

That PR addresses the new [target size](https://www.w3.org/TR/WCAG22/#target-size-minimum) success criterion introduced in WCAG 2.2. Fix #318

## Description of problem From time to time, a document changes its shortname to a new one. In such cases, the new history link (using the new shortname) will only...

Fix #338 To be merged after sync'ing with @tabatkins and @marcoscaceres.

See https://github.com/w3c/web-locks/pull/97

Repository's names are case-insensitive and should be treated as such by the repo manager. Currently, the repo manager will not find the repository after a {lower,upper}case renamin. see https://github.com/w3c/ash-nazg/issues/229

rename Web API to Browser API

4

Following a discussion with @dontcallmedom, the term 'Browser API' will probably be less ambiguous than 'Web API'

Title and ED updates aren't taken into account if the document was already published on the same day

1

This happened for reporting-1 (see https://github.com/w3c/browser-specs/pull/574).