Closed Bug 6159 Opened 26 years ago Closed 26 years ago

checked attribute on checkboxes returns the opposite of what it should

Categories

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

x86
Linux
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: sdm, Assigned: ramiro)

References

()

Details

(Whiteboard: will fix this one tonight (6/16/1999))

Take a close look at the source to the above url and the 3 lines that look like this: document.getElementById('tb_display').checked return false if checked, and true if not checked. I had to hide this bug in the interface by calling the checkbox Show instead of Hide. This worked correctly a while back. If you can't reproduce, take the checked='checked' attributes off of the 3 <html:input type='checkbox' ... lines in the form, and try again.
Assignee: vidur → pollmann
This bugs for you!
Assignee: pollmann → ramiro
Ramiro, I too am seeing some strangeness in the GTK native widgets. I'm using a fresh build from this morning. The checkbox is not changing state of the first click, and it is reporting back a state of "checked" when it is not first checked. Another test case: (You can peek and poke all DOM attributes here) blueviper/forms/testDisplay.cgi?element=CheckboxInput
Status: NEW → ASSIGNED
Target Milestone: M6
yes, its a bug in code i wrote. ill fix it soon. thanks
marking assigned m6.
Target Milestone: M6 → M7
marking m7. i cant make m6 for this bugs.
*** Bug 6881 has been marked as a duplicate of this bug. ***
*** Bug 7695 has been marked as a duplicate of this bug. ***
*** Bug 8051 has been marked as a duplicate of this bug. ***
Assignee: ramiro → pavlov
Status: ASSIGNED → NEW
I'll fix this one today.
Status: NEW → ASSIGNED
Whiteboard: will fix this one tonight (6/16/1999)
Assignee: pavlov → ramiro
Status: ASSIGNED → NEW
i have a fix for this. reassignin to myself.
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
Status: RESOLVED → VERIFIED
Checked testcase from blueviper. Verified on 1999-07-13-08 build.
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.