Hello Anatoly,
anatoly techtonik wrote: > API changelog contains ambiguous notes about JQuery API change. > ... > message of r6715 it is almost clear (well, if you are experienced > enough to know what is that handler it mentions), http://trac.edgewall.org/changeset/6715 assumes that conflicting js libraries will only get used from specific IRequestHandlers. It doesn't account for possible use of conflicting libraries anywhere else, like in secondary handlers (e.g. admin pages providers) or even from a wiki macro (by the use of late scripts). That could eventually be fixed one day, so I would advise you to use jQuery as if you were always in noConflict mode, like all jQuery code in Trac does. Wrap your jQuery code in .js files like this: (function($){ ... })(jQuery); And the ready() callback in .html templates should be written like this: jQuery(document).ready(function($) { ... }); Most jQuery plugins (if not all) are also written like that, so those are good conventions to follow anyway. > P.S. Should there be a more appropriate place with documentation on > available JS API? > In the to-be-written TracDev/Javascript page? -- Christian --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
