Thanks. Actually, I worked on avoiding that function but there is too
much dynamic stuff being done and it would require a lot of work to
change my system. I actually created my own crude .click() function
of sorts that worked like this.
function nFunc(id) {
if(document.getElementById(id)){
nfunc=document.getElementById(id).onclick;
var go=new nfunc;
}
};
It worked, but I had a different problem with that method that I
cannot recall right now.
Anyway, I seem to have been able to make it work by doing this.
<a id='StartNew' name='StartNew' class='selected' href='#'
onclick="return false">Place an Order</a>
Simply putting the "return false" in the click function as you
demonstrated still redirected the browser to the same url with a # at
the end. But using onclick="return false" makes things work as
desired (no page redirect or scrolling). I guess that the inline
onclick event AND the DOM onclick event are both executed somehow? I
am not familiar enough with DOM to know why that works.
~ Jeremy
On Apr 2, 2:03 pm, "Brandon Aaron" <[EMAIL PROTECTED]> wrote:
> You can just return false at the end of your click handler method:
>
> $('a').click(function() {
> doStuff();
> doSomeMore();
> return false; // stop event
>
> });
>
> However, that might still not stop IE, there is a ticket for this to
> be fixed btw. I would just avoid using the .click() to trigger the
> event all together and just call the methods as they are in the click
> handler. Hopefully this will be fixed in 1.1.3.
>
> --
> Brandon Aaron
>
> On 4/2/07, tpneumat <[EMAIL PROTECTED]> wrote:
>
> > Thanks Brandon.
>
> > Yes. Thanks, that does help. I knew it was related to the click
> > event all along, but I just didnt' know what was different about the
> > click. The problem stems from using javascript: void(0); on my
> > hyperlinks. See this site.
> >http://blog.reindel.com/2006/08/11/a-hrefjavascriptvoid0-avoid-the-void/
>
> > I tested this theory, and in fact, if I use the href='#' method, the
> > problem goes away. However, now I am trying to figure out where to
> > put the return false; to prevent the # from appending to the url.
>
> > I will let you know my final solution.
>
> > Thanks,
>
> > Jeremy
>
> > On Apr 2, 1:20 pm, "Brandon Aaron" <[EMAIL PROTECTED]> wrote:
> > > Jeremy,
>
> > > My first guess as to the source of this weirdness would be the last
> > > line of the script tag at the bottom of the body tag.
>
> > > $('#StartNew').click();
>
> > > The click() event handling is one of the major things that changed in
> > > 1.1.1. It also fires the actual click event of the element if one
> > > exists. That would be the first point of investigation.
>
> > > I would also consider applying the patch in ticket 1061 to see if it
> > > changes anything.
>
> > > Ticket 1061:http://dev.jquery.com/ticket/1061
>
> > > Hopefully some of this helps ... if not I'll try dig a little deeper.
>
> > > --
> > > Brandon Aaron
>
> > > On 4/2/07, tpneumat <[EMAIL PROTECTED]> wrote:
>
> > > > I am feeling all alone on this one. I guess I will have to take
> > > > Andrew's suggestion and do browser detection to deliver a different
> > > > version of jquery forIE6. Kind of disappointed with that, however.
>
> > > > Jeremy
>
> > > > On Mar 30, 2:48 pm, "Jeremy Dill" <[EMAIL PROTECTED]> wrote:
> > > > > Yes. And 1.1.1. Packed or unpacked, same result.
>
> > > > > -----Original Message-----
> > > > > From: Mike Alsup [mailto:[EMAIL PROTECTED]
> > > > > Sent: Friday, March 30, 2007 2:23 PM
> > > > > To: [EMAIL PROTECTED]; jQuery Discussion
> > > > > Subject: Re: [jQuery] New version of jquery andIE6bugs
>
> > > > > > Using jquery-1.0.4.js - NO PROBLEMS
> > > > > >http://www.dilltree.com/test/jtest104.html
>
> > > > > > Using jquery-latest.pack.js - CSS ISSUES ON REFRESH.
> > > > > >http://www.dilltree.com/test/jtest112.html
>
> > > > > Jeremy,
>
> > > > > Have you tried an unpacked version of 1.1.2?
>
> > > > > _______________________________________________
> > > > > jQuery mailing list
> > > > > [EMAIL PROTECTED]://jquery.com/discuss/
