jQuery: The Write Less, Do More JavaScript Library

Ticket #2079 (closed bug: wontfix)

Opened 8 months ago

Last modified 6 months ago

javascript.options.strict warnings [1.2.2b]

Reported by: Byron Assigned to: anonymous
Type: bug Priority: major
Milestone: 1.2.2 Component: core
Version: 1.2.1 Keywords:
Cc: Needs: Patch

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

warn_fix1.diff (1.1 kB) - added by Vegar 8 months ago.
Not very complex fix for the warnings on init

Change History

Changed 8 months ago by joern

  • status changed from new to closed
  • resolution set to wontfix

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

Changed 8 months ago by Vegar

Not very complex fix for the warnings on init

Changed 8 months ago by Vegar

  • status changed from closed to reopened
  • resolution deleted

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 8 months ago by brandon

  • status changed from reopened to closed
  • resolution set to wontfix

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

Changed 8 months ago by Byron

  • status changed from closed to reopened
  • resolution deleted

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 7 months ago by 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

Changed 6 months ago by brandon

  • status changed from reopened to closed
  • resolution set to wontfix
Note: See TracTickets for help on using tickets.