Open
Bug 411177
Opened 17 years ago
Updated 2 years ago
select element onchange event (in XSL documents only) is now case sensitive
Categories
(Core :: DOM: UI Events & Focus Handling, defect, P5)
Tracking
()
NEW
People
(Reporter: will_lentz, Unassigned)
References
Details
(Keywords: regression, testcase)
Attachments
(1 file)
526 bytes,
application/x-tar
|
Details |
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•17 years ago
|
||
Comment 2•16 years ago
|
||
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
Updated•16 years ago
|
Flags: wanted1.9.0.x? → wanted1.9.0.x+
Comment 4•16 years ago
|
||
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
Comment 5•6 years ago
|
||
Decreasing the priority as no update for the last 2 years on this bug. See https://github.com/mozilla/bug-handling/blob/master/policy/triage-bugzilla.md#how-do-you-triage about the priority meaning.
Priority: P1 → P5
Assignee | ||
Updated•5 years ago
|
Component: Event Handling → User events and focus handling
Updated•2 years ago
|
Severity: normal → S3
Comment 6•2 years ago
|
||
The bug assignee is inactive on Bugzilla, so the assignee is being reset.
Assignee: jonas → nobody
You need to log in
before you can comment on or make changes to this bug.
Description
•