Overloading methods in a separate partial definition is invalid

[tidoust]

The Sanitizer API overloads methods already defined in HTML, such as Document.parseHTMLUnsafe() (HTML, Sanitizer API).

That is forbidden by Web IDL: it imposes that "Operations must not be overloaded across interface, partial interface, interface mixin, and partial interface mixin definitions." (see Overloading).

I suspect that you're doing that on purpose, know what you're doing, and that the final goal is to upstream these definitions to HTML. I also don't see any immediate workaround (apart from relaxing the constraint in Web IDL, perhaps?)

In the meantime, I note that this creates a practical problem: the updated IDL defined in the Sanitizer API cannot reach Web Platform Tests (interfaces/sanitizer-api.idl) because one of the guarantees that we enforce in Webref on the way to Web Platform Tests is that the Web IDL as a whole, merging the IDL defined across specs, is valid.

[annevk]

Can we annotate them in some way that they're not indexed? It shouldn't really matter until it's standardized.

[otherdaniel]

Would this work? #210

That looks a bit dorky, since it just renames the methods in questions by adding a __TO_BE_MERGED suffix. But it should make the tools happy again.

[tidoust]

Can we annotate them in some way that they're not indexed?

Yes, adding class=extract would work to exclude the IDL from indexing.

The renames obviously work as well.

We can also make do with the problem from a tooling perspective. We would create a patch on our side to exclude the IDL and make the tools happy again. That's less ideal for us, of course ;) Anyway, I was more reporting the problem so what you are aware of it and not surprised that propagation to WPT appears broken.