Do you have any more information regarding this? Some simple markup? It's hard to tell from what you've inferred here.
--John On Mon, Feb 9, 2009 at 11:05 AM, Dimi Paun <[email protected]> wrote: > > > On Mon, 2009-02-09 at 10:44 -0500, John Resig wrote: >> >> This should be fixed now. >> http://dev.jquery.com/changeset/6190 > > Good. Any timeline for 1.3.2? > > Also, since we upgraded to 1.3.1 we've noticed some > strange errors in IE6 that make no sense. > > This is embarrassing, but we've noticed that if we > patch jQuery like so: > > @@ -1044,12 +1043,19 @@ > return letter.toUpperCase(); > }); > > - if ( set ) > + if ( set ) { > + //weird fix for IE6 > + console.log(""); > elem[ name ] = value; > + } > > The error goes away! (console.log() is Firebug's API). > > The error that we see is something about "Invalid attribute" > when we had a normal assigment of: > > cmnts_shown = has_cmnts; > > (where both of these are regular variables holding a boolean). > > Moreover, we would keep getting the same error even if we > replaced this with > > cmnts_shown = true; > > The hack that we use is horrible, I know, any idea what this > might be all about? Or how we can try to trace it down? > > -- > Dimi Paun <[email protected]> > Zipalong, Inc. > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jQuery Development" 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/jquery-dev?hl=en -~----------~----~----~----~------~----~------~--~---
