Item9080: $.noConflict() causes much confusion

pencil
Priority: Urgent
Current State: Closed
Released In:
Target Release: n/a
Applies To: Engine
Component:
Branches:
Reported By: CrawfordCurrie
Waiting For:
Last Change By: CrawfordCurrie
I just had to deal with another user who was wailing:

"why don't any of my jQuery calls work"

The answer was, of course, $.noConflict().

I have no problem with noConflict being enabled by default; but I do have a problem with this not being mentioned anywhere in the documentation.

The following need to document the use of $.noConflict():

-- CrawfordCurrie - 31 May 2010

Later, OK, I admit my ignorance; I don't know exactly why this user was having problems, all I know is that switching to jQuery() instead of $() fixed it for them. Under what circumstances is noConflict actually included? How does a user detect this situation? These are the questions that have to be answered in the doc.

-- CrawfordCurrie - 31 May 2010

This is another instance of an RTFM.

-- MichaelDaum - 31 May 2010

If RTFM stands for "Rewrite The F***ing Manual", I totally agree. When I went to look for information on this topic, I found it is totally obscure. To say "use $" and then just a few lines later say "if you want to use $, you have to do this" is very confusing.

I improved it in UsingJQueryWithFoswiki but the plugin doc also needs fixing.

-- CrawfordCurrie - 31 May 2010

Done.

-- CrawfordCurrie - 04 Jun 2010

 

ItemTemplate edit

Summary $.noConflict() causes much confusion
ReportedBy CrawfordCurrie
Codebase
SVN Range
AppliesTo Engine
Component
Priority Urgent
CurrentState Closed
WaitingFor
Checkins distro:ab492e2f2106
TargetRelease n/a
ReleasedIn
Topic revision: r4 - 04 Jun 2010, CrawfordCurrie
The copyright of the content on this website is held by the contributing authors, except where stated elsewhere. See Copyright Statement. Creative Commons License    Legal Imprint    Privacy Policy