Closed Bug 372445 Opened 18 years ago Closed 16 years ago

onchange handler is ignored on textareas

Categories

(Core :: DOM: UI Events & Focus Handling, defect)

1.8 Branch
x86
Linux
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: alex, Unassigned)

References

()

Details

User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; ru; rv:1.8.1.2) Gecko/20060601 Firefox/2.0.0.2 (Ubuntu-edgy) Build Identifier: Mozilla/5.0 (X11; U; Linux x86_64; ru; rv:1.8.1.2) Gecko/20060601 Firefox/2.0.0.2 (Ubuntu-edgy) Firefox 2.0.0.2 on Ubuntu Linux does not call onchange event handler on textarea any more. Both 2.0 on Linux and 2.0.0.2 on Windows does not have the problem so it looks like a platform-specific regression. Neither inline onchange= handler nor DOM-added handlers are called. Provided URL demonstrates the issue. Reproducible: Always
Version: unspecified → 2.0 Branch
Bug 370521 is marked as being fixed in Firefox 2.0.0.2. Are you using a Firefox 2.0.0.2 build from mozilla.org or from Ubuntu?
This is official Ubuntu 6.10 build marked as: Mozilla/5.0 (X11; U; Linux x86_64; ru; rv:1.8.1.2) Gecko/20060601 Firefox/2.0.0.2 (Ubuntu-edgy) I'm going to report it to them.
This bug in Ubuntu tracker, for easy reference: https://launchpad.net/firefox/+bug/89349
The problem appears to exist as well on Seamonkey 1.1, see also http://tonnerre.users.bsdprojects.net/tmp/formtest.html Also, this seems related to Bug 355367 so there appears to be a general problem
Assignee: nobody → events
Component: General → Event Handling
Product: Firefox → Core
QA Contact: general → ian
Version: 2.0 Branch → 1.8 Branch
Ubuntu has got 2.0.0.3 as of today so the bug is not relevant for me. I'd close if Tonnerre's comment were taken into account elsewhere.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
No bug or patch referenced as the code fix. (It's not clear if bug 355367 was actually the solution or not.)
Resolution: FIXED → WORKSFORME
Component: Event Handling → User events and focus handling
You need to log in before you can comment on or make changes to this bug.