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 found what caused my problem - it was my own mixin (that, in turn, uses PathJS library). I'm not sure where exactly the error is, but switching this mixin off restored the functionality of autocomplete. I'm trying to switch to jquery-hashchange plugin and check what happens. On Sat, Nov 9, 2013 at 10:38 PM, François Facon <francois.fa...@atos.net>wrote: > 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 client side and you just want to add some jQuery Plugin in your > page. > > > 2013/11/9 John <j...@quivinco.com> > > > 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 that there may be some dependency on prototype or other > > significant defects. > > > > John > > ----- Original Message ----- > > From: Ilya Obshadko > > To: Tapestry users > > Sent: Saturday, November 09, 2013 7:38 AM > > Subject: jQuery autocomplete stops working when SUPPRESS_PROTOTYPE is > > true > > > > > > This is weird, and I can't find what causes the error. > > > > If JQuerySymbolConstants.SUPPRESS_PROTOTYPE is set to true, > autocomplete > > list disappears on hover. If I switch it back to false, everything > starts > > working correctly again. Any ideas? > > > > -- > > Ilya Obshadko > > > -- Ilya Obshadko
