121202 - Can't set 'checked' property of <Input type=checkbox > while loading a page

Status: RESOLVED FIXED

(Core :: Layout: Form Controls, defect)

Description

[Ivan Sagalaev]

First look into the source of the URL - it's self-explanatory.
Here goes a description:
The page creates a form with 3 checkboxes. Then inline JavaScript tries to set
each checkbox' 'checked' to 'true' and fails.
After 3 seconds the same JavaScript code is called again (through setTimeout)
and works good.

P.S. When I insert, say, window.alert(elements[i]) before setting 'checked' the
code works good for the first time too.

Comment 1

[Stephen P. Morse]

Reassigning

Comment 2

[Boris Zbarsky [:bzbarsky]]

confirming on linux 2002-01-19-21.  jkeiser?

Comment 3

[John Keiser (jkeiser)]

The problem is probably that the frame doesn't exist yet.  Pretty sure this will
go away with bug 108308.

Comment 4

[rods (gone)]

->>

Comment 5

[Ivan Sagalaev]

Interesting note: if I use elements[i].setAttribute('checked') instead of
setting directly elements[i].checked=true everything works.

Does Mozilla use different APIs for accessing a property directly or through a
DOM method?

Comment 6

[Boris Zbarsky [:bzbarsky]]

.checked and setAttribute("checked") do entirely different things.  One sets an
attribute on a node (equivalent to actually editing the HTML).  The other
changes the value of a DOM property.  The fact that the initial value of the DOM
property is decided based on the value of the attribute is the only thing that
ties the two together.

Comment 7

[Ivan Sagalaev]

Thanks for explanation.

My misunderstanding was because I've seen the .checked property on a W3C in the
DOM1 spec. I did think that setting properties through setAttribute or
propertie's  corresponding interface should differ just in syntax... Now I see
the true difference :-)

Comment 8

[John Keiser (jkeiser)]

Oops, I set the dependency wrong before, it was bug 108307, which has landed,
and fixed this bug with it.