#1295 closed bug (fixed)
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: |
Description
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 (2)
Changed 15 years ago by
| Attachment: | fix-jquery-1.1.2.diff added |
|---|
comment:1 Changed 15 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
This is fixed with the new event system under the hood in 1.1.3a.