915552 - Adding non-existing names to implicitJSContext in Bindings.conf doesn't cause an error

Status: NEW

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

Description

[(no longer active)]

This can confuse people if they manage to do a typo in their implicitJSContext, and waste a few minutes on that.

Alternatively, somebody can try to teach me how to type, but that sounds much more difficult than being a bit more pedantic in the bindings generator.

Comment 1

[Boris Zbarsky [:bzbarsky]]

Given that properties/methods can be ifdefed, but bindings.conf cannot, this could be hard to do...

Comment 2

[Andrew McCreight [:mccr8]]

We could warn if a property isn't present, but is a small edit distance from a property that is present. ;)

Comment 3

[Boris Zbarsky [:bzbarsky]]

Hmm.  Or we could just do the "fail if not present" thing and worry about the ifdef situation if it comes up...  People shouldn't be using implicitJSContext anyway.