User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.8.1) Gecko/20061010 Firefox/2.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.8.1) Gecko/20061010 Firefox/2.0 onChange event is not launched if input has been changed with form field history (when i chose the field value in the history with mouse or keyboard arrows) Reproducible: Always Steps to Reproduce: 1. write a form with something like "<input type="text" onChange="alert('it works !');" /> 2. try this form few times completing the field with keyboard 3. try this form completingto complete the field with history Actual Results: on change event is not launched Expected Results: i expect that it would be launched
Still present with the latest nightly build of Minefield: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20061109 Minefield/3.0a1
Confirming this. And it's a regression from Firefox 1.5. A commenter in #firefox reported it in Linux as well.
Severity: major → normal
Status: UNCONFIRMED → NEW
Component: General → Autocomplete
Ever confirmed: true
OS: Windows XP → All
Product: Firefox → Toolkit
QA Contact: general → autocomplete
Version: unspecified → 1.8 Branch
Summary: onChange event is not launched if input has been changed with form field history → onChange event is not launched if input has been changed with form field history (autocomplete)
*** Bug 354697 has been marked as a duplicate of this bug. ***
This bug makes me sad....i rely on the onChange event for text boxes to pre-load remaining elements of forms. Now, i'm going to have to go back to using things like buttons and "onClicking". ...again, very sad:(
Regression Range on trunk 2006070504 works 2006070604 fails Bonsai checkin list doesn't bring any obvious results to me. This bug also affects 1.8.1.x on a post-branch checkin. Should I search that regression range also?
Checkins to module PhoenixTinderbox between 2006-07-05 03:00 and 2006-07-06 05:00 : http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&module=PhoenixTinderbox&branch=HEAD&branchtype=match&dir=&file=&filetype=match&who=&whotype=match&sortby=Date&hours=2&date=explicit&mindate=2006-07-05+03&maxdate=2006-07-06+05&cvsroot=%2Fcvsroot
Well, I was going to post this bug, but meanwhile found out I'm not the only one complaining. And, this bug is already 2 years old and isn't even assigned?! It seams to me that this one is a little to serious for getting by... The way I see it, it means Firefox offers a way to change fields without triggering "onchange" events. That renders them rather useless, doesn't it? Maybe stopping adding new features and start fixing the "classic" bugs isn't such a bad idea... That said, keep up the great work :-)
The patch in bug 388558 (which is a dup of this one, I think) fixes the problem.
Status: NEW → RESOLVED
Last Resolved: 11 years ago
No longer depends on: 388558
Resolution: --- → DUPLICATE
Duplicate of bug: 388558
You need to log in before you can comment on or make changes to this bug.