This is expected behavior. Updated test case: http://jsfiddle.net/3ksqX/5/

Each copy of jQuery has its own event list. When you manually .trigger("click") or .click() the copy of jQuery does most of the work. It has to:

• Start at the event target (the innermost element clicked)
• Run any associated event handlers that **this copy of jQuery** knows about; it doesn't know about lists held by other copies but it does know about the inline onclick handlers.
• Bubble up the DOM repeating the process until it reaches window.
• For all DOM methods **except click**, run the DOM method if the default action has not been stopped with event.preventDefault(). See #12652 for why this exception exists.

If you need to bridge two copies of jQuery you could a click handler on one copy that triggered a similar click on the other jQuery copy. Really though, two copies of jQuery in a page should be avoided.

I saw the other ticket, but this really seems inconsistent to me, because it works with other elements, but not with links.

And it is sad, but I don't really have any knowledge about the other jQuery versions. I mean, I could write some

if (!jQuery) { doc.write('<script src="own-jquery.js"></scr'+'ipt>'); }

code but it seemed a bad idea. And then I have to put up with all the old versions of jQuery's quirks, not to mention if for some reason they use $.noConflict too, when attaching event listeners, than there is no way of triggering a click event, that runs all the handlers that were attached is any way. At least not with jQuery. This is so sad.

But, thank you really!