Sorry for the delay in getting back to this (I love my work, it just
doesn't love me back).

...oh boyyyy. I knew it would be a stupid typo. I was referencing
src="jquery.js" when, in fact, I should have been referencing
src="jquery-1.2.1.js". (I swear I looked at the error console a dozen
times!!)

http://www.ixwa.com/jquery_test.html

How's THAT for the Darwin award of the year? I've been doing this a
long time, but dumb mistakes seem to know no limits.

(sheepishly) Hehe, sorry all. jQuery is lovely.


Now I think I'll just go and play with my Legos.


On Oct 1, 5:23 am, Wizzud <[EMAIL PROTECTED]> wrote:
> Ummm... I don't want to sound pedantic but all I've done is confirm that the
> code you posted works fine when I modify the source of the jquery script
> file to suit my environment. I can't say whether or not something is
> interfering with it on your system because I don't know what else you have
> on your page.
>
> As Michael has already said, if you give us an example we can get at then it
> could be resolved immediately. If your client does not want 'his' page made
> (temporarily) public, then either chop out any sensitive stuff (and
> re-test!), make up a new one (and re-test!), or simply don't tell him (we
> won't snitch). Probably the first thing to do is take 30 seconds to do
> exactly what I did - lift the exact code you posted and paste it into a new
> page, close it off properly, and confirm that it works.
>
> Regarding jQuery playing nicely with others, every effort has been made to
> ensure that it will do just that. So if you have one of those 'others' on
> your page, and it turns out that that is what's causing the problem, then it
> would assist everybody greatly to know about the conflict and provide a
> means for avoiding/circumventing it. If it happens to be proprietary script
> that is causing interference then we may be able to help there too.
>
>
>
> cmbtrx wrote:
>
> > See previous reply; I am not Spock (and yes, I should have included
> > sample code--doh. sorry)
>
> > Thanks for testing this out...seems then that something is interfering
> > with jQuery functionality. So, um, that does not bode well for my
> > using jQuery...is it prone to not playing nice with others? Just
> > wondering out loud...
>
> > On Sep 28, 2:40 pm, Wizzud <[EMAIL PROTECTED]> wrote:
> >> @cmbtrx
> >> I have just lifted the code directly from your second post, tagged
> >> </body></html> after the anchor, and it worked first time (Firefox and
> >> IE7).
> >> I can only suggest that you check that the path to the jquery.js source
> >> file
> >> is correct for wherever you are running it, as that is the *only* thing
> >> that
> >> would prevent the alert from showing.
>
> >> (Actually, thinking about it, it's not the only thing that could prevent
> >> the
> >> link activating, because you state that there is more html below the
> >> link,
> >> and it is possible - though unlikely - for that to prevent the link
> >> activation, so I would suggest that for testing you remove any extraneous
> >> code from your page.)
>
> >> Bratty missives beget bratty missives. Frustration can be understood,
> >> accepted, and usually resolved - but responses are far more likely when
> >> the
> >> request is couched in polite terms, and with as much relevant information
> >> as
> >> possible.
>
> >> cmbtrx wrote:
>
> >> > Shucks, I knew it was too good to be true.
>
> >> > This ass/troll/clueless individual thanks you for making this group
> >> > forum now begin to sound like every other developer's resource on the
> >> > web: well-intentioned but ultimately crippled by the bratty missives
> >> > of a few self-important detractors.
>
> >> > Feel free to share your own insights next time--it might in fact be an
> >> > opportunity for you to learn something that perhaps you never knew you
> >> > needed to know.
>
> >> > On Sep 27, 8:28 pm, Robert Koberg <[EMAIL PROTECTED]> wrote:
> >> >> Hi,
>
> >> >> I am new to jquery. Haven't had any problems that couldn't be solved
> >> by
> >> >> the docs or a search. I am amazed that an ass/troll/clueless
> >> individual
> >> >> gets so much play.
>
> >> >> whatev,
> >> >> -Rob
>
> >> >> On Thu, 2007-09-27 at 21:54 +0000, cmbtrx wrote:
> >> >> > lol looks just like mine.
>
> >> >> > I sense that a stupid typo is fast approaching the direction of this
> >> >> > conversation...
>
> >> >> > Nice little site that--pastie.
>
> >> >> > On Sep 27, 5:45 pm, "Richard D. Worth" <[EMAIL PROTECTED]> wrote:
> >> >> > > On 9/27/07, cmbtrx <[EMAIL PROTECTED]> wrote:
>
> >> >> > > > OK, forgive my tone here...I'm actually quite flabbergasted.
>
> >> >> > > > I ***FINALLY*** get around to trying out jquery.
>
> >> >> > > > Oh, I'm sure that quite obviously I'm doing something wrong,
> >> >> because
> >> >> > > > after following the first few paragraphs of the "How JQuery
> >> Works"
> >> >> > > > section (clicking a link launches an alert box...uh ok, no fine)
> >> it
> >> >> > > > does absolutely nothing.
>
> >> >> > > After following the first few paragraphs of
>
> >> >> > >  http://docs.jquery.com/How_jQuery_Works
>
> >> >> > > my page looks something like this:
>
> >> >> > >  http://pastie.caboo.se/101553
>
> >> >> > > This works for me. Perhaps you could compare what you have to mine
> >> >> and see
> >> >> > > if you can find a significant difference. Or if mine works, use it
> >> as
> >> >> a
> >> >> > > starting point. Good luck, and let us know how it turns out.
>
> >> >> > > - Richard
>
> >> --
> >> View this message in
> >> context:http://www.nabble.com/uhhh.......WAT--tf4530903s15494.html#a12946285
> >> Sent from the JQuery mailing list archive at Nabble.com.
>
> --
> View this message in 
> context:http://www.nabble.com/uhhh.......WAT--tf4530903s27240.html#a12975828
> Sent from the jQuery General Discussion mailing list archive at Nabble.com.

Reply via email to