It looks like a lot of properties to define event handlers are not available. See the exhaustive list here: http://www.whatwg.org/specs/web-apps/current-work/multipage/elements.html#elements-in-the-dom
I think this is a dup. Currently we add onfoo listeners in nsDOMClassInfo, but we should change that.
(In reply to comment #1) > I think this is a dup. Currently we add onfoo listeners in nsDOMClassInfo, but > we should change that. A dup of which bug? Actually, this bug could be spitted in two: 1. oninput, oninvalid, onchange (and probably some other) properties doesn't work if set. 2. all on<eventName> are not valid properties of HTMLElement. Is 2. the dup?
Created attachment 499013 [details] [diff] [review] Patch v1
Approval request: there is no way to check if oninput or oninvalid is supported by Firefox by an author because |"oninput" in inputElement| will always return false for the moment. I think we should make sure it will work given that we support the events.