Incorrect auto-type in HTML spec

[jakearchibald]

https://html.spec.whatwg.org/multipage/webappapis.html#dom-manipulation-task-source

From the refs database:

text:      DOM manipulation task source
type:      interface
spec:      html
shortname: html
level:     1
status:    snapshot
url:       https://html.spec.whatwg.org/multipage/webappapis.html#dom-manipulation-task-source
export:    True
normative: True
for_:      []

I don't see why this is type: interface, since it isn't exported as an interface.

I wonder if it thinks it's an interface because it starts "DOM"? In which case, maybe terms containing spaces should never be auto-detected as interfaces?

[jakearchibald]

The only suspect I can find is https://github.com/tabatkins/bikeshed/blob/main/bikeshed/unsortedJunk.py#L545, but that would type as "function" rather than interface.

[domenic]

This is due to Shepherd (or Bikeshed?) guessing that any definition that starts with "DOM" is an interface.

We've asked multiple times (https://github.com/whatwg/html/pull/6360#issuecomment-773533763, https://github.com/whatwg/wattsi/pull/149) for Shepherd to stop applying these heuristics to HTML. But so far the maintainers have refused to do so. It's very frustrating.

[jakearchibald]

Hah, I tried the same data-dfn-type="dfn" fix and ran into the same issues.

[jyasskin]

If the problem is in Shepherd, it'll be fixed by #1761, which @tabatkins is actively working on again.