HTML shouldn't <dfn> Document

[jyasskin]

A Bikeshed file containing {{Document}} complains that:

LINK ERROR: Multiple possible 'idl' refs for 'Document'.
Arbitrarily chose the one in html.
If this is wrong, insert one of the following lines into a <pre class=link-defaults> block:
spec:dom; type:interface; text:Document
spec:html; type:interface; text:Document

HTML's is only a partial interface, so it shouldn't use markup that overrides DOM's definition for other specs. I'm not sure if the right thing to do is to remove the <dfn> tag, mark it with data-noexport="", or something else. @tabatkins, can you advise?

[zcorpan]

"Document" links in the HTML spec itself should be internal links, not to the DOM spec.

[annevk]

Can't we just mark it as partial interface somehow?

[tabatkins]

This is another case for "some way to opt a DFN out of Bikeshed processing". I'll go ahead and add that today.

(partials are handled by Bikeshed at the parsing level - if it notices that you're defining a partial interface, it forces the interface name to be an A, rather than choosing A/DFN based on whether there's already an instance of that interface defined elsewhere. There's nothing at the definition-contract level that indicates something is a partial definition.)

[tabatkins]

Done. Setting data-dfn-lt="" should drop it from Bikeshed's database, so nothing can autolink to it at all. (If this works as it should, we can use it for all the other things that were "unexported" just to try and hide them from Bikeshed.)

[annevk]

@tabatkins though if it parses it as partial, it should be clear too it cannot be "the" <dfn>. Anyway, adding data-dfn-lt="" should be fine.

[tabatkins]

Right, that's what I'm saying - in a Bikeshed document, Bikeshed knows about partial interfaces, and prevents them from becoming definitions by default. But there's nothing in the data model that indicates an interface definition came from a partial block, so if a non-Bikeshed spec has partial <dfn>Foo</dfn> {...};, I can't do anything about it.