On May 16, 2006, at 3:05 PM, prla wrote:
>
> Thanks so much for taking the time to reproduce my scenario, Bob.
>
> As much as it embarasses me saying this, the bug turned out to be
> in my
> code (obviously) and it's as simple as this. I was writing:
>
> var cb = INPUT({'type':'checkbox', 'name':'itemCheckbox',
> 'onclick':'toggleBar()', 'value':item.id}, null);
>
> instead of:
>
> var cb = INPUT({'type':'checkbox', 'name':'itemCheckbox',
> 'onclick':'toggleBar()', 'value':item.id});
>
> That surplus 'null' 2nd argument was making a world of a difference,
> apparently. I thought it was needed. Your test output showed me
> otherwise and now it works. Though I'm sure the patch you pointed
> me to
> earlier also helped, because this name attribute thing is a known IE6
> issue from what I could gather.
null is only required if you're leaving out attributes, not the
content. The surplus null for content definitely does not make any
difference at all. The code path is simply a no-op if you specify
nulls for content.
I just tried to reproduce to make sure but couldn't make anything
strange happen. Your issue must've been something else.
-bob
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"MochiKit" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/mochikit
-~----------~----~----~----~------~----~------~--~---
