You could also put the .click events inside a document.ready(). Then they can click away, but no results until the event handler is set after document.ready.
On Mar 20, 12:30 pm, James <james.gp....@gmail.com> wrote: > That's the default of how web browsers. You can work around it such as > by setting the display of those <a> to hidden in your CSS, and use > Javascript to show it upon page ready. Depending on how your website > works, this may mean your page would not work properly if users do not > have Javascript enabled. > > On Mar 20, 5:48 am, HippieX <jlrober...@gmail.com> wrote: > > > I have a problem I am sure others have encountered. I have .click() > > events attached to <a> links in my web page, but the user is clicking > > the links before the document.ready(); fires causing unexpected > > results. Is there anyway to stop this from happening? > > > Thanks, > > > Jeff
