Skip to main content

Bug Tracker

Side navigation

#2079 closed bug (wontfix)

Opened December 19, 2007 07:57PM UTC

Closed February 17, 2008 06:34AM UTC

Last modified October 14, 2008 10:25AM UTC

javascript.options.strict warnings [1.2.2b]

Reported by: Byron Owned by:
Priority: major Milestone: 1.2.2
Component: core Version: 1.2.1
Keywords: Cc:
Blocked by: Blocking:
Description

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
Attachments (1)
  • warn_fix1.diff (1.1 KB) - added by Vegar December 21, 2007 08:07PM UTC.

    Not very complex fix for the warnings on init

Change History (6)

Changed December 20, 2007 10:12PM UTC by joern comment:1

resolution: → wontfix
status: newclosed

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

Changed December 21, 2007 08:09PM UTC by Vegar comment:2

resolution: wontfix
status: closedreopened

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.

Changed December 22, 2007 08:57PM UTC by brandon comment:3

resolution: → wontfix
status: reopenedclosed

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

Changed December 23, 2007 08:17AM UTC by Byron comment:4

resolution: wontfix
status: closedreopened

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?

Changed January 18, 2008 09:36PM UTC by davidserduke comment:5

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

Changed February 17, 2008 06:34AM UTC by brandon comment:6

resolution: → wontfix
status: reopenedclosed