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)
Tracking
()
VERIFIED
FIXED
M7
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.
Updated•26 years ago
|
Assignee: vidur → pollmann
Comment 1•26 years ago
|
||
This bugs for you!
Updated•26 years ago
|
Assignee: pollmann → ramiro
Comment 2•26 years ago
|
||
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
Assignee | ||
Updated•26 years ago
|
Status: NEW → ASSIGNED
Target Milestone: M6
Assignee | ||
Updated•26 years ago
|
Target Milestone: M6 → M7
Status: NEW → ASSIGNED
Whiteboard: will fix this one tonight (6/16/1999)
Assignee | ||
Updated•26 years ago
|
Assignee: pavlov → ramiro
Status: ASSIGNED → NEW
Comment 10•26 years ago
|
||
i have a fix for this.
reassignin to myself.
Updated•26 years ago
|
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
Comment 11•26 years ago
|
||
Checked testcase from blueviper. Verified on 1999-07-13-08 build.
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•