javascript.options.strict warnings [1.2.2b]

[Byron]

some new warnings have been introduced in 1.2.2b

When jQuery initializes the following warnings are thrown

reference to undefined property jQuery.cache[id][name]
http://code.jquery.com/jquery-1.2.2b.js
Line 661

reference to undefined property elem.nodeType
http://code.jquery.com/jquery-1.2.2b.js
Line 1793

The Following Warnings are fired when an animation is performed:

reference to undefined property optall.queue
http://code.jquery.com/jquery-1.2.2b.js
Line 2830

reference to undefined property elem.nodeType
http://code.jquery.com/jquery-1.2.2b.js
Line 1011

reference to undefined property opt.queue
http://code.jquery.com/jquery-1.2.2b.js
Line 2985

[joern]

Resolving those makes the code a lot more complex without actually solving any problems.

[Vegar]

Not very complex fix for the warnings on init

[Vegar]

I've attached a fix for the init-warnings (that doesn't make the code a lot more complex). And it solves a problem: It makes the javascript console readable when using jQuery.

[brandon]

You can't just check for elem.length as that will be false when it is === 0.

[Byron]

It doesnt makes sense to leave this unfixed, until now, all strict warnings issues have been resolved. ​http://dev.jquery.com/search?q=strict+warnings whats changed?

[davidserduke]

What has changed is the "fixes" hurt performance. So far we have decided that isn't worth it. See this thread for more info:

​http://groups.google.com/group/jquery-dev/browse_thread/thread/f2926d95fcafb18