Skip to main content

Bug Tracker

Side navigation

#1295 closed bug (fixed)

Opened June 15, 2007 02:04AM UTC

Closed June 15, 2007 05:31AM UTC

Last modified March 15, 2012 01:09AM UTC

Conflict with Omniture javascript

Reported by: trischuk Owned by:
Priority: major Milestone: 1.1.3
Component: event Version: 1.1.2
Keywords: Cc:
Blocked by: Blocking:

I ran into a conflict between jQuery's and Omniture's javascript libs. The conflict seems to be the way each lib does onload handling. If Omniture's libs are loaded after jQuery's (which is required for us right now), then Omniture saves jQuery's handlers but executes them in a different OO context so "this" is not set to what jQuery expects. I've made a fix which I think does the right thing, but I haven't delved deeply into jQuery's code.

I am attaching a diff -c of the fix I made against jQuery 1.1.2.

Attachments (1)
Change History (1)

Changed June 15, 2007 05:31AM UTC by brandon comment:1

resolution: → fixed
status: newclosed

This is fixed with the new event system under the hood in 1.1.3a.