[jQuery] Re: No reaction with $('a').click(), OK with dispatchEvent(...)

>> At the moment I'm not so interested in the right/smart way to write an >> tag. It's more interesting to me to see what the jQuery click() >> function can and cannot do ok, then read the source. we're trying to offer solutions to the problem, but if you just want some info on what jQuery's clic

[jQuery] Re: No reaction with $('a').click(), OK with dispatchEvent(...)

Hi, I'm not quite sure what you try to show me with that $('#a3').click (...stuff...) below, but I can tell you what I just found out: The difference I've mentioned between my clickAt($('#a1')[0]) and $ ('#a1').click(), and also with #a3, occurs in Safari and Opera, but in Firefox (3.0.3 and 3.5.5

Re: [jQuery] Re: No reaction with $('a').click(), OK with dispatchEvent(...)

Jon schrieb: and one (#a3) that links to this Google Groups page. With the latter I observe the same difference as with #a1: my clickAt($('#a3')[0]) works, but $('#a3').click() doesn't. Bug or feature? Sorry I can't follow you. I added this to Firebug on your Testpage: $('#a3').click( functio

[jQuery] Re: No reaction with $('a').click(), OK with dispatchEvent(...)

Hi, At the moment I'm not so interested in the right/smart way to write an tag. It's more interesting to me to see what the jQuery click() function can and cannot do, and it could also be interesting to know why it "fails" where my clickAt(...) works. I have now extended my test page

[jQuery] Re: No reaction with $('a').click(), OK with dispatchEvent(...)

if you have to keep your JavaScript inline, you should use the onclick attribute instead of using the "javascript:" pseudo-protocol. it was never fully standardized, and is a lingering piece of old-school JavaScript usage. so for your example above, use: #a1 an even better solution (as you are alr