Closed Bug 618948 Opened 9 years ago Closed 9 years ago
.oninput and foo .oninvalid should be working
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?
Summary: Define oninput, oninvalid, onchange and other properties related to events on HTMLElement → foo.oninput and foo.oninvalid should be working
Assignee: nobody → mounir.lamouri
Status: NEW → ASSIGNED
Attachment #499013 - Flags: review?(Olli.Pettay)
Attachment #499013 - Flags: review?(Olli.Pettay) → review+
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.
Whiteboard: [passed-try][needs-review] → [passed-try][needs-approval]
Attachment #499013 - Flags: approval2.0? → approval2.0+
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla2.0b9
You need to log in before you can comment on or make changes to this bug.