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

NEW
Unassigned

Status

()

5 years ago
3 years ago

People

(Reporter: Ehsan, Unassigned)

Tracking

Trunk
x86
Mac OS X
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [tw-dom])

(Reporter)

Description

5 years ago
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.
Given that properties/methods can be ifdefed, but bindings.conf cannot, this could be hard to do...
We could warn if a property isn't present, but is a small edit distance from a property that is present. ;)
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.
You need to log in before you can comment on or make changes to this bug.