select element onchange event (in XSL documents only) is now case sensitive

NEW
Assigned to

Status

()

Core
Event Handling
P1
normal
11 years ago
10 years ago

People

(Reporter: Will Lentz, Assigned: sicking)

Tracking

({regression, testcase})

Trunk
x86
Windows XP
regression, testcase
Points:
---
Bug Flags:
blocking1.9.1 -
wanted1.9.1 +
wanted1.9.0.x +

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

11 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.11) Gecko/20071127 Firefox/2.0.0.11
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b3pre) Gecko/2008010705 Minefield/3.0b3pre

With FireFox 2.0 in an XSL document you can have a form with:
  <select onChange="alert('1');"> ...

With the latest Firefox, a form in an XSL document with the above code doesn't work.  Instead, the code needs to be changed to:
  <select onchange="alert('1');"> ...

Note that in HTML documents either of the above versions works.

Shouldn't onchange be case insensitive?


Reproducible: Always

Steps to Reproduce:
I'm going to attach a test case:
1. Browse to test.xml
2. changing the select element for "opt1 with onChange" will not trigger an alert.  But - changing the element for "opt2 with onchange" will correctly trigger the alert.



Expected Results:  
Everything in this test case works fine in Firefox 2.0.0.11.  Only the latest nightly 3.0 beta shows a problem.
(Reporter)

Comment 1

11 years ago
Created attachment 295809 [details]
Test case demonstrating problem
I can reproduce this on Windows XP/Vista.

No alert: 2006100213
Alert: 2006100222

Regression range:
http://bonsai.mozilla.org/cvsquery.cgi?module=PhoenixTinderbox&date=explicit&mindate=2006-10-02+12%3A00&maxdate=2006-10-02+23%3A00
Seems to be caused by Bug 221335.
Blocks: 221335
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: regression, testcase
Version: unspecified → Trunk
Indeed. This is a bug, and the regression looks right.
Flags: wanted1.9.1+
Assignee: nobody → jonas
Flags: wanted1.9.1+
Flags: wanted1.9.0.x?
Flags: blocking1.9.1+
Priority: -- → P3
Flags: wanted1.9.0.x? → wanted1.9.0.x+
On second thought this is not a blocker, but we'd love to fix it soon!
Flags: wanted1.9.1+
Flags: blocking1.9.1-
Flags: blocking1.9.1+
Priority: P3 → P1
You need to log in before you can comment on or make changes to this bug.