815404 - add annotation to prevent static IDL operations from generating functions with an nsISupports* global

Status: NEW

(Core :: DOM: Core & HTML, defect, P5)

Description

[Cameron McCormack (:heycam)]

Some static functions, like CSS.supports(), do not need access to the global object, so it ought to be possible to say (in Bindings.conf or in the IDL) that the nsISupports* global argument is not added.

Comment 1

[Kyle Huey (Exited; not receiving bugmail, old account, do not use)]

Does it really matter?  The compiler will optimize it out.

Comment 2

[Boris Zbarsky [:bzbarsky]]

I'm not sure the compiler can in fact optimize out the binding end of this (the actual extraction of the global from the call information, etc).

Comment 3

[Peter Van der Beken [:peterv]]

Attachment: Detect the right signature at compile time

This uses templates to detect if a function with the right signature exists, either with or without a globalobject. Because of the templates the error messages are a bit verbose if no function with the right signature exists. Not sure the complexity is worth it. There are some smaller things we should do if we don't take the whole thing (like have separate types for worker/non-worker globalobject).

Comment 4

[Peter Van der Beken [:peterv]]

Attachment: Detect the right signature at compile time

Moved the part about the type of the global object to bug 816088.

Comment 5

[Firefox Bug Husbandry Bot]

https://bugzilla.mozilla.org/show_bug.cgi?id=1472046

Move all DOM bugs that haven’t been updated in more than 3 years and has no one currently assigned to P5.

If you have questions, please contact :mdaly.