Re: jQuery autocomplete stops working when SUPPRESS_PROTOTYPE is true

2013-11-09 Thread Ilya Obshadko
Thanks, that makes sense. Any ideas on hashchange event handling compatibility? On Sun, Nov 10, 2013 at 3:29 AM, François Facon wrote: > Oups! My bad. > if you set JQuerySymbolConstants. > SUPPRESS_PROTOTYPE at *false*, the tapestry core components will use a > prototype implementations. > see h

Re: jQuery autocomplete stops working when SUPPRESS_PROTOTYPE is true

2013-11-09 Thread François Facon
Oups! My bad. if you set JQuerySymbolConstants. SUPPRESS_PROTOTYPE at *false*, the tapestry core components will use a prototype implementations. see https://github.com/got5/tapestry5-jquery/wiki/FAQ and the first commit about SUPPRESS_PROTOTYPE https://github.com/got5/tapestry5-jquery/commit/0fcf7

Re: jQuery autocomplete stops working when SUPPRESS_PROTOTYPE is true

2013-11-09 Thread Ilya Obshadko
Well, looks like listening to the history events conflicts with jquery/autocomplete mixin somehow. jquery-hashchange plugin has same issue: when hashchange event is handled, autocomplete no longer works. On Sun, Nov 10, 2013 at 12:31 AM, Ilya Obshadko wrote: > I don't completely understand, do

Re: jQuery autocomplete stops working when SUPPRESS_PROTOTYPE is true

2013-11-09 Thread Ilya Obshadko
I don't completely understand, do you really mean setting SUPPRESS_PROTOTYPE to *false* allows tapestry to use Prototype implementations? I'm expecting that SUPPRESS_PROTOTYPE, literally, suppresses usage of Prototype and allows to switch to jQuery completely. Is this right? Seems like I have foun

Re: 5.4-alpha-24 JS bug

2013-11-09 Thread Michał Gruca
Hi George, check if correct .js libs are specified to import. When lib is not found I'm getting the same page template and as it's not a valid .js file I'm getting error. Or maybe on of libs is referring to something that does not exist (or was moved?) Regards, Michal On Sat, Nov 9, 2013 at 5:5

Re: jQuery autocomplete stops working when SUPPRESS_PROTOTYPE is true

2013-11-09 Thread François Facon
if you set JQuerySymbolConstants.SUPPRESS_PROTOTYPE at true, the tapestry core components will use a prototype implementations. In this case, communication between core components and jQuery plugin is much more difficult. this option is fine when you are using a lots of prototype code on the clien

Re: jQuery autocomplete stops working when SUPPRESS_PROTOTYPE is true

2013-11-09 Thread John
Hi, I have found problems with jquery such as submit buttons not working when inside zones that get refreshed, and likewise for ajax dialog links. I have had to remove quite a bit of the jquery use from my current project, I'm even considering pulling it entirely from the product. It appears t

Re: jQuery autocomplete stops working when SUPPRESS_PROTOTYPE is true

2013-11-09 Thread François Facon
May be another javascript function redefined the hover event handler. what version do you use? any javascript console error? to diagnose this type of problem, you can disable other components one by one. could you share your .tml? 2013/11/9 Ilya Obshadko > This is weird, and I can't find what