Closed Bug 12741 Opened 21 years ago Closed 20 years ago

Checkboxes don't change state when using onClick & another onClick error.

Categories

(Core :: DOM: Core & HTML, defect, P2)

x86
Windows 98
defect

Tracking

()

VERIFIED WORKSFORME

People

(Reporter: pervago, Assigned: joki)

Details

(Whiteboard: [nsbeta2+])

Attachments

(1 file)

(Mozilla M9 - Windows 98 Spanish Version)

Checkboxes don't change state when using onClick handler regardless
of it's return value:

<form action="#">
These checkboxes do not change their state regardless of return value
of onClick handler:<br><br>
<b>Initially checked</b><br><br>
<input type="checkbox" checked onClick="alert('Clicked');return true">
<input type="checkbox" checked onClick="alert('Clicked');return false">
<br><br><b>Initially unchecked</b><br><br>
<input type="checkbox" onClick="alert('Clicked');return true">
<input type="checkbox" onClick="alert('Clicked');return false">
</form>
When you click on any of the checkboxes you get expected alert() message but unchecked checkboxes remain unchecked and checked remain checked.
Opera(3.6)/NN4/IE5 all get this right.

2. Opera/NN4/IE5 when using onClick handler change state of checkbox BEFORE transferring control to handler but Mozilla doesn't.
Attached file Test case
HTML DOM bugs are M11/P2 for Vidur.
Assignee: vidur → lshadoff
Whiteboard: [MAKINGTEST] lshadoff@websorcerer.com
Status: NEW → ASSIGNED
Target Milestone: M11 → M12
m12
Target Milestone: M12 → M14
m14
Bulk moving old [makingtest] code to new makingtest keyword. Sorry for the spam! 
Keywords: makingtest
How come this is still M14? M14 is already out!
Nominating nsbeta2. We have to start drawing a line on DOM0 backward 
compatibility; these bugs are supposed to be a high priority for nsbeta2 per the 
beta2 criteria.
Keywords: nsbeta2
Whiteboard: [MAKINGTEST] lshadoff@websorcerer.com → lshadoff@websorcerer.com
lshadoff@websorcerer.com, just to confirm, are you a C++ engineer who has 
volunteered to take responsibility for fixing this bug for nsbeta2, or as this 
bug been assigned to you by mistake? (Sorry, I don't know you--many thanks if 
you're lending a hand!)

Setting to [nsbeta2+]. Totally basic DOM0.
Whiteboard: lshadoff@websorcerer.com → [nsbeta2+]lshadoff@websorcerer.com
Target Milestone: M14 → M17
No reply from lshdaoff@websorcerer.com - reassigning to ekrock@netscape.com for 
triage, and removing makingtest info.

Eric - I guess he assigned it to himself while makeing the test case (which 
seems to now be done). This is confirmed still a problem on 2000-06-11.

Gerv
Assignee: lshadoff → ekrock
Status: ASSIGNED → NEW
Keywords: makingtest
Whiteboard: [nsbeta2+]lshadoff@websorcerer.com → [nsbeta2+]
Assignee: ekrock → jst
Reassigning to jst@netscape.com. Nice catch Gerv--thanks!
Reassigning to our event man.
Assignee: jst → joki
You know its somehow not surprising, though it probably should be, that while 
jumping about this bug hasn't actually been tested.  Marking WORKSFORME.
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
WORKSFORME too. marking verified. Checkbox is not supposed to change state when 
it returns false, and that is what is happening, so it works fine.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.