Skip to main content

Bug Tracker

Side navigation

#8722 closed bug (worksforme)

Opened March 31, 2011 04:46AM UTC

Closed April 16, 2011 10:53PM UTC

jQuery 1.5.1 is placing target variable into the global namespace

Reported by: anonymous Owned by: anonymous
Priority: undecided Milestone: 1.next
Component: global Version: 1.5.1
Keywords: Cc:
Blocked by: Blocking:
Description

The jQuery 1.5.1 library is placing an internal variable called target into the global namespace. I tested jQuery 1.4.1 and the same issue cannot be found. If the target variable is changed this can interrupt the internal workings of jQuery.

Attachments (0)
Change History (5)

Changed April 01, 2011 12:43AM UTC by timmywil comment:1

component: unfiledglobal
owner: → anonymous
status: newpending

Thank you for submitting a bug report to the jQuery project! I checked all globals on a page with jQuery 1.5.2 and was unable to reproduce your issue. http://i.imgur.com/87DxC.png Please provide a test case on http://jsfiddle.net so that we can review the issue further.

Changed April 08, 2011 02:53AM UTC by dmethvin comment:2

_comment0: Fixes #8722. Remove try/catch used by #3533 to fix the IE Table Colon Blow bug, and instead check for colon in the event name. Thanks to daguej for scoping this out -- a colonoscopy you might say. \ Changeset: 98d83ef85f41fefb40a14eec24c6804c088bbeeb1302269272984364
_comment1: (incorrectly closed this bug due to a transposition of the ticket number)1302271823021755
resolution: → fixed
status: pendingclosed

(incorrectly closed this bug due to a transposition of the ticket number .. should have been #8272)

Changed April 08, 2011 01:28PM UTC by dmethvin comment:3

resolution: fixed
status: closedreopened

Changed April 08, 2011 01:28PM UTC by dmethvin comment:4

status: reopenedpending

Still need a test case for this.

Changed April 16, 2011 10:53PM UTC by addyosmani comment:5

resolution: → worksforme
status: pendingclosed

As per timmywil, I too was unable to reproduce this after going through the globals in 1.5.2. Please feel free to re-open if you can provide a test case that reproduces the issue.