[Proto-Scripty] Re: IE issue when with 'new Element' : expected identifier, string or number

2008-10-31 Thread T.J. Crowder
> So it's probably a good and safe practice to quote > all the element property names, right? Not necessarily a bad idea, although in practice I suspect the list of reserved words[1] is pretty set at this point (and I should have said JavaScript or ECMAScript, not JScript; "class" is reserved by

[Proto-Scripty] Re: IE issue when with 'new Element' : expected identifier, string or number

2008-10-30 Thread cyiam
You can try replacing the option class with className. On Oct 30, 1:08 pm, "Brandon Casci" <[EMAIL PROTECTED]> wrote: > Thanks was it. Thanks for the help. Though a slew of new IE issues are > popping up now, fun fun!. So it's probably a good and safe practice to quote > all the element property

[Proto-Scripty] Re: IE issue when with 'new Element' : expected identifier, string or number

2008-10-30 Thread Brandon Casci
Thanks was it. Thanks for the help. Though a slew of new IE issues are popping up now, fun fun!. So it's probably a good and safe practice to quote all the element property names, right? On Thu, Oct 30, 2008 at 12:02 PM, T.J. Crowder <[EMAIL PROTECTED]>wrote: > > Hi, > > Just put 'class' in quo

[Proto-Scripty] Re: IE issue when with 'new Element' : expected identifier, string or number

2008-10-30 Thread T.J. Crowder
Hi, Just put 'class' in quotes, it's a reserved word in JScript. The example in the docs[1] has it in quotes for that reason, I suspect. [1] http://www.prototypejs.org/api/element HTH, -- T.J. Crowder tj / crowder software / com On Oct 30, 3:49 pm, Brandon <[EMAIL PROTECTED]> wrote: > Internet