Closed
Bug 370521
Opened 18 years ago
Closed 18 years ago
TextArea not firing onchange event
Categories
(Core :: DOM: Events, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: mozilla.dev, Assigned: smaug)
References
()
Details
(Keywords: regression, testcase, verified1.8.1.2, Whiteboard: regression from bug 357684)
Attachments
(5 files)
|
1.45 KB,
patch
|
MatsPalmgren_bugz
:
review+
bzbarsky
:
superreview+
|
Details | Diff | Splinter Review |
|
1.33 KB,
patch
|
MatsPalmgren_bugz
:
review+
bzbarsky
:
superreview+
|
Details | Diff | Splinter Review |
|
2.76 KB,
text/html
|
Details | |
|
2.80 KB,
text/html
|
Details | |
|
3.05 KB,
patch
|
Details | Diff | Splinter Review |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.2) Gecko/20070214 Firefox/2.0.0.2
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.2) Gecko/20070214 Firefox/2.0.0.2
In FireFox 2.0.0.2 release candidates RC2 and pre RC3 the onchange event no longer fires on a textarea.
Reproducible: Always
Steps to Reproduce:
1. Visit the attached URL
2. Type something into the textarea
3. Click off the textarea
Actual Results:
Nothing alerts
Expected Results:
The page should alert "test"
Updated•18 years ago
|
Assignee: nobody → events
Component: Form Manager → DOM: Events
Product: Firefox → Core
QA Contact: form.manager → ian
Version: unspecified → 1.8 Branch
Comment 1•18 years ago
|
||
Get an alert:
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.2pre) Gecko/20061227 BonEcho/2.0.0.2pre
No alert:
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.2pre) Gecko/20061228 BonEcho/2.0.0.2pre
Regression window:
http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&module=all&branch=MOZILLA_1_8_BRANCH&branchtype=match&dir=&file=&filetype=match&who=&whotype=match&sortby=Date&hours=2&date=explicit&mindate=2006-12-27+03%3A33&maxdate=2006-12-28+03%3A32&cvsroot=%2Fcvsroot
Perhaps bug 357684, CC'ing mats and bz.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: blocking1.8.1.2?
Updated•18 years ago
|
Keywords: regression
| Assignee | ||
Comment 2•18 years ago
|
||
Argh, I guess we need the same thing for textareas what was added for input elements in Bug 357684. Will test that now.
| Assignee | ||
Comment 3•18 years ago
|
||
| Assignee | ||
Comment 4•18 years ago
|
||
These needs some testing.
| Assignee | ||
Updated•18 years ago
|
Attachment #255244 -
Flags: review?(mats.palmgren)
| Assignee | ||
Updated•18 years ago
|
Attachment #255246 -
Attachment is patch: true
Attachment #255246 -
Attachment mime type: text/x-patch → text/plain
Attachment #255246 -
Flags: review?(mats.palmgren)
| Assignee | ||
Comment 5•18 years ago
|
||
Mats, if you have any good tests, could you try those
| Assignee | ||
Comment 6•18 years ago
|
||
Assignee: events → Olli.Pettay
Status: NEW → ASSIGNED
| Assignee | ||
Updated•18 years ago
|
| Assignee | ||
Updated•18 years ago
|
Attachment #255244 -
Flags: superreview?(bzbarsky)
| Assignee | ||
Updated•18 years ago
|
Attachment #255246 -
Flags: superreview?(bzbarsky)
Comment 7•18 years ago
|
||
Comment on attachment 255244 [details] [diff] [review]
for trunk
sr=bzbarsky. Does <select> need something like this too?
Attachment #255244 -
Flags: superreview?(bzbarsky) → superreview+
Comment 8•18 years ago
|
||
Comment on attachment 255246 [details] [diff] [review]
for 1.8
sr=bzbarsky.
Attachment #255246 -
Flags: superreview?(bzbarsky) → superreview+
| Assignee | ||
Comment 9•18 years ago
|
||
As far as I see <select> dispatches 'change' whenever something actually changes, not on 'blur'.
Comment 10•18 years ago
|
||
Tab to a combobox, use the up/down arrow keys to change the selection, then tab out. That should fire onchange on blur.
| Assignee | ||
Comment 11•18 years ago
|
||
(In reply to comment #10)
> Tab to a combobox, use the up/down arrow keys to change the selection, then tab
> out. That should fire onchange on blur.
>
Ah, when size=1. Seems to work even without a patch.
| Assignee | ||
Comment 12•18 years ago
|
||
| Assignee | ||
Comment 13•18 years ago
|
||
Comment 14•18 years ago
|
||
Comment on attachment 255244 [details] [diff] [review]
for trunk
r=mats
Attachment #255244 -
Flags: review?(mats.palmgren) → review+
Comment 15•18 years ago
|
||
Comment on attachment 255246 [details] [diff] [review]
for 1.8
r=mats
Attachment #255246 -
Flags: review?(mats.palmgren) → review+
| Assignee | ||
Updated•18 years ago
|
Attachment #255246 -
Flags: approval1.8.1.2?
| Assignee | ||
Comment 16•18 years ago
|
||
Checked in to trunk
Status: ASSIGNED → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
Comment 17•18 years ago
|
||
Forgive my possible bug spam, but how is this resolved without having been checked into the branch yet?
Comment 18•18 years ago
|
||
RESOLVED FIXED status applies to the bug's status on the trunk. fixed1.8.x keywords are applied when the patch is committed to the specific branch.
| Assignee | ||
Comment 19•18 years ago
|
||
Attachment #255711 -
Flags: review?(bzbarsky)
| Assignee | ||
Comment 20•18 years ago
|
||
I think another option for branch is to back out bug 357684.
At least .0.2. would work like .0.1
| Assignee | ||
Updated•18 years ago
|
Attachment #255711 -
Flags: review?(bzbarsky)
Updated•18 years ago
|
Flags: blocking1.8.1.2? → blocking1.8.1.3+
| Assignee | ||
Comment 21•18 years ago
|
||
Whoever verifies the bug for branch, note that the testcase from
reporter is http://ld.livecache.net/F/5618588/Test.html, not the
testcase I attached.
Comment 22•18 years ago
|
||
(In reply to comment #21)
> Whoever verifies the bug for branch, note that the testcase from
> reporter is http://ld.livecache.net/F/5618588/Test.html, not the
> testcase I attached.
>
Hi, thanks :)
verified for 1.8.1.2 using this testcase.
Build: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.8.1.2) Gecko/2007021917 Firefox/2.0.0.2 Mnenhy/0.7.5.0 (RC5) also on Windows Vista Ultimate.
Keywords: testcase,
verified1.8.1.2
Comment 23•18 years ago
|
||
I also tested the backout of bug 357684 and the http://ld.livecache.net/F/5618588/Test.html passes with
Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.2) Gecko/20070219 Firefox/2.0.0.2
Leaving the verified1.8.1.2 keyword in place, since we know this works with Firefox 2.0.0.2 rc5, but we need to make sure we address this issue again.
If we decide to take the fix in bug 357684 in the future, we will also have to take the patch in this bug and verify that all test cases work.
Comment 24•18 years ago
|
||
Comment on attachment 255246 [details] [diff] [review]
for 1.8
Moving nomination so we don't miss it.
Attachment #255246 -
Flags: approval1.8.1.2? → approval1.8.1.4?
Comment 25•18 years ago
|
||
Hi Guys,
Though this is fixed on windows platform, it doesn't seems to be working on ubuntu.
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.2) Gecko/20060601 Firefox/2.0.0.2 (Ubuntu-edgy)
Thanks
Comment 26•18 years ago
|
||
Comment on attachment 255246 [details] [diff] [review]
for 1.8
approved for 1.8.1.4, a=dveditz for release-drivers
Attachment #255246 -
Flags: approval1.8.1.4? → approval1.8.1.4+
Updated•18 years ago
|
OS: Windows XP → All
| Assignee | ||
Comment 27•18 years ago
|
||
(In reply to comment #26)
> (From update of attachment 255246 [details] [diff] [review])
> approved for 1.8.1.4, a=dveditz for release-drivers
>
This patch was a regression fix for bug 357684, but that was
backed out from branch.
Comment 28•18 years ago
|
||
The question is whether we want to reland it....
| Assignee | ||
Comment 29•18 years ago
|
||
Marking blocking1.8.1.4? for now.
Bug 357684 has blocking1.8.1.4-
Flags: blocking1.8.1.4+ → blocking1.8.1.4?
Comment 30•18 years ago
|
||
Comment on attachment 255246 [details] [diff] [review]
for 1.8
clearing patch branch approval while we straighten out the issues with the regressing bug.
Attachment #255246 -
Flags: approval1.8.1.4+
Comment 31•18 years ago
|
||
Clearing blocking flag. If we do end up taking bug 357684 on the branch we'll want to approve a regression-fixing patch in that bug.
Flags: blocking1.8.1.4? → wanted1.8.1.x?
Whiteboard: regression from bug 357684
Updated•18 years ago
|
Flags: wanted1.8.1.x? → wanted1.8.1.x+
You need to log in
before you can comment on or make changes to this bug.
Description
•