Open
Bug 915552
Opened 11 years ago
Updated 2 years ago
Adding non-existing names to implicitJSContext in Bindings.conf doesn't cause an error
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
NEW
People
(Reporter: ehsan.akhgari, Unassigned)
Details
(Whiteboard: [tw-dom])
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•11 years ago
|
||
Given that properties/methods can be ifdefed, but bindings.conf cannot, this could be hard to do...
Comment 2•11 years ago
|
||
We could warn if a property isn't present, but is a small edit distance from a property that is present. ;)
Comment 3•11 years ago
|
||
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.
Whiteboard: [tw-dom]
Assignee | ||
Updated•5 years ago
|
Component: DOM → DOM: Core & HTML
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•