Thanks Tim :-) AARON ROSENZWEIG / Chat 'n Bike <http://www.chatnbike.com/> e: aa...@chatnbike.com <mailto:aa...@chatnbike.com> t: (301) 956-2319
> On Feb 28, 2019, at 9:31 PM, D Tim Cummings <t...@triptera.com.au> wrote: > > Hi Aaron > > I found a solution. It can be fixed by changing the way the container tags > were nested in AjaxAutocomplete. I have created a pull request with the fix. > I would appreciate if you could test it. > > https://github.com/wocommunity/wonder/pull/906 > <https://github.com/wocommunity/wonder/pull/906> > > Regards > > Tim Cummings > > >> On 26 Feb 2019, at 00:26, Aaron Rosenzweig <aa...@chatnbike.com >> <mailto:aa...@chatnbike.com>> wrote: >> >> Hi Tim and WOFriends, >> >> Thanks for the update - that could be what we were experiencing. Our page >> was rather long… it might have showed the auto-completer way down out of >> view - I don’t know - but that is what you appear to be suggesting and very >> well could be it. >> >> For us, the “solution” was to make a fork of current wonder and replace the >> version of prototype with the blessed one for the version of Scriptaculous >> in Wonder. I believe that was Prototype v1.7.0 (going from memory, not >> verifying right now). It’s whatever version that originally shipped with >> Scriptaculous and there is not a newer version of Scriptaculous to upgrade >> too - that project appears dead. >> >> So it’s not ideal - next time we update Wonder we’ll have to replace >> prototype - or build something different. Anyway - I stuck my finger in the >> dike and moved on. >> AARON ROSENZWEIG / Chat 'n Bike <http://www.chatnbike.com/> >> e: aa...@chatnbike.com <mailto:aa...@chatnbike.com> t: (301) 956-2319 >> >> >> >>> On Feb 25, 2019, at 12:54 AM, D Tim Cummings <t...@triptera.com.au >>> <mailto:t...@triptera.com.au>> wrote: >>> >>> Aaron >>> >>> I have just updated to the latest Wonder and found that the Ajax >>> Autocomplete is working but the location of the drop-down menu is located >>> much further down the screen rather than next to the textfield where the >>> user is typing. I need to fix it also so I am keen to hear if you come >>> across a solution. >>> >>> For example running the old Wonder and the new Wonder on the same data, the >>> div where the suggestions are have different values of 'top'. Sometimes the >>> differences are big and sometimes small so I think it is related to other >>> html on the same page. This is why it looks like it is working on simple >>> examples. >>> >>> OLD GENERATED HTML >>> >>> <div id="ZContainere_0_0_11_11_1_97_3_3_0_3_21_div" style="position: >>> absolute; top: 0px; left: 0px; z-index: 1000;"> >>> <div class="auto_complete" id="e_0_0_11_11_1_97_3_3_0_3_21_div" >>> style="position: absolute; left: 670px; top: 855px; width: 144px; "> >>> <ul> >>> <li class="">FMFRANK</li> >>> >>> >>> NEW GENERATED HTML >>> >>> <div id="ZContainere_0_0_11_11_1_97_3_3_0_3_21_div" style="position: >>> absolute; top: 0px; left: 0px; z-index: 1000;"> >>> <div class="auto_complete" id="e_0_0_11_11_1_97_3_3_0_3_21_div" >>> style="position: absolute; left: 670px; top: 1197px; width: 138px; "> >>> <ul> >>> <li class="">FMFRANK</li> >>> >>> >>> In this example, 855px correctly places the drop-down menu while 1197px >>> places the drop-down menu off the screen. >>> >>> Regards >>> >>> Tim Cummings >>> >>> >>>> On 14 Feb 2019, at 06:03, Aaron Rosenzweig <aa...@chatnbike.com >>>> <mailto:aa...@chatnbike.com>> wrote: >>>> >>>> Yes it is a bit of a mystery. >>>> >>>> Without any errors in the JS console of the web browser and no errors in >>>> the java console either… it is silently not working. >>>> >>>> When I say “not working” mean the suggestions in the drop-down menu do not >>>> display. There is no menu - it seems like there is no autocomplete at all. >>>> No border, no remnant, nothing. >>>> >>>> Thank you Samuel for taking time to make a simpler example and finding >>>> that it still worked. I cannot explain it. There must be something else >>>> subtle that is not clear. Maybe it *is* working but is somehow not visible >>>> with z-index and whatnot… no idea really just spouting BS now. >>>> AARON ROSENZWEIG / Chat 'n Bike <http://www.chatnbike.com/> >>>> e: aa...@chatnbike.com <mailto:aa...@chatnbike.com> t: (301) 956-2319 >>>> >>>> >>>> >>>>> On Feb 13, 2019, at 2:41 PM, Samuel Pelletier <sam...@samkar.com >>>>> <mailto:sam...@samkar.com>> wrote: >>>>> >>>>> Aaron, >>>>> >>>>> I notice that you did not use the item and display string, i.e. use only >>>>> a text form of auto complete. I tried to simplify one use and it still >>>>> works. >>>>> >>>>> Did the value got set when user is typing and the suggestion getter >>>>> called ? >>>>> >>>>> You may have another problem in the page that block the javascript >>>>> execution during the initialization... >>>>> >>>>> Another thing that may differ is the usage (or non usage) of javascript >>>>> files .min versions, I use the full versions even on production. >>>>> >>>>> Samuel >>>>> >>>>> >>>>>> Le 13 févr. 2019 à 14:01, Aaron Rosenzweig <aa...@chatnbike.com >>>>>> <mailto:aa...@chatnbike.com>> a écrit : >>>>>> >>>>>> Hi, actual neither of us are using “local” I didn’t remember the default >>>>>> and assumed it was true. Appears the default is false, I was just >>>>>> explicitly setting it. >>>>>> >>>>>> So I don’t know why it works for you but not for us with Prototype 1.7.3 >>>>>> >>>>>> AARON ROSENZWEIG / Chat 'n Bike <http://www.chatnbike.com/> >>>>>> e: aa...@chatnbike.com <mailto:aa...@chatnbike.com> t: (301) 956-2319 >>>>>> >>>>>> >>>>>> >>>>>>> On Feb 13, 2019, at 2:00 PM, Aaron Rosenzweig <aa...@chatnbike.com >>>>>>> <mailto:aa...@chatnbike.com>> wrote: >>>>>>> >>>>>>> Hi Everyone especially Samuel! >>>>>>> >>>>>>> This is what our code looks like: >>>>>>> >>>>>>> <wo:AjaxAutoComplete value = "$typedValueByUser" list = "$suggestions" >>>>>>> isLocal = "$false" afterUpdateElement = "$afterUpdateElementAction" >>>>>>> frequency = "0.2" /> >>>>>>> >>>>>>> <wo:AjaxSubmitButton functionName = >>>>>>> "$submitUserSelectedValueCustomFunction" updateContainerID = >>>>>>> "$checkMarkContainerID" action = "$userSelectedFreeFormAddressText" /> >>>>>>> >>>>>>> Note: the "afterUpdateElementAction" is javascript that clicks the >>>>>>> submit button. >>>>>>> >>>>>>> One difference, besides linguistic preference, is that yours is local >>>>>>> but ours is not. We hand off to a service to scrub what is partially >>>>>>> typed and then come back with suggestions. Note the “isLocal = false” >>>>>>> >>>>>>> I have not tried the AjaxExample project. Literally our apps stopped >>>>>>> working, people started screaming that the sky is falling, and to put >>>>>>> out the fire I replaced the version of Prototype. >>>>>>> >>>>>>> AARON ROSENZWEIG / Chat 'n Bike <http://www.chatnbike.com/> >>>>>>> e: aa...@chatnbike.com <mailto:aa...@chatnbike.com> t: (301) >>>>>>> 956-2319 >>>>>>> >>>>>>> >>>>>>>> On Feb 13, 2019, at 1:51 PM, Samuel Pelletier <sam...@samkar.com >>>>>>>> <mailto:sam...@samkar.com>> wrote: >>>>>>>> >>>>>>>> Hi Aaron, >>>>>>>> >>>>>>>> I have the latest wonder and my AjaxAutoCompletes are working as >>>>>>>> expected. >>>>>>>> >>>>>>>> Have you tried the AjaxExample project ? >>>>>>>> >>>>>>>> Maybe we have a different usage. I use it like this: >>>>>>>> <wo:AjaxAutoComplete list = "$enseignants" item = "$enseignant" >>>>>>>> displayString = "$enseignant.contact.nomComplet" value = >>>>>>>> "$textToFindEnseignant" selection = "$selectedEnseignant" >>>>>>>> style="display: inline-block; margin-bottom:0; width:120px;" >>>>>>>> afterUpdateElement = "function(){ajouteEnseignant();}"/> >>>>>>>> <wo:AjaxSubmitButton functionName = "ajouteEnseignant" >>>>>>>> updateContainerID = "blocPeriodeEditor" action = "$ajouterEnseignant" >>>>>>>> class="tiny button" style="margin-bottom:0;"/> >>>>>>>> >>>>>>>> Samuel >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>>> Le 12 févr. 2019 à 16:26, Aaron Rosenzweig <aa...@chatnbike.com >>>>>>>>> <mailto:aa...@chatnbike.com>> a écrit : >>>>>>>>> >>>>>>>>> Hi Everyone, >>>>>>>>> >>>>>>>>> We discovered after recently updating Wonder… that Prototype 1.7.3 is >>>>>>>>> not compatible with Scriptaculous 1.9 (what is in Wonder). >>>>>>>>> >>>>>>>>> At least, it is not compatible with the autocomplete functionality at >>>>>>>>> a minimum. >>>>>>>>> >>>>>>>>> For the moment we have made a local branch of Wonder and employed >>>>>>>>> Prototype 1.7.0 as that is the last blessed version for >>>>>>>>> Scriptaculous. It’s possible that 1.7.2 might be ok, have not tried, >>>>>>>>> but 1.7.3 does not work. >>>>>>>>> AARON ROSENZWEIG / Chat 'n Bike <http://www.chatnbike.com/> >>>>>>>>> e: aa...@chatnbike.com <mailto:aa...@chatnbike.com> t: (301) >>>>>>>>> 956-2319 >>>>>>>>> >>>>>>>>> >>>>>>>>>> On Jan 21, 2019, at 5:18 AM, Michael Schmiedgen <schmied...@takwa.de >>>>>>>>>> <mailto:schmied...@takwa.de>> wrote: >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>>> We are using 1.7.3 for years with no known problems. >>>>>>>>>>> Where is a pull request? :-) >>>>>>>>>> >>>>>>>>>> Here: >>>>>>>>>> https://github.com/wocommunity/wonder/pull/893 >>>>>>>>>> <https://github.com/wocommunity/wonder/pull/893> >>>>>>>>>> >>>>>>>>>> :) >>>>>>>>>> >>>>>>>>>> Michael >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> ___________________________ >>>>>>>>>> >>>>>>>>>> Michael Schmiedgen, BSc >>>>>>>>>> Senior Software Engineer >>>>>>>>>> >>>>>>>>>> Takwa GmbH >>>>>>>>>> Friedrich-List-Str. 36 >>>>>>>>>> 99096 Erfurt GERMANY >>>>>>>>>> >>>>>>>>>> Tel +49 361 6534096 >>>>>>>>>> Fax +49 361 6534097 >>>>>>>>>> Mail schmied...@takwa.de <mailto:schmied...@takwa.de> >>>>>>>>>> Web http://www.takwa.de/ <http://www.takwa.de/> >>>>>>>>>> ___________________________ >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Amtsgericht Jena HRB 112964 >>>>>>>>>> Geschäftsführung: Ingo Buchholz >>>>>>>>>> _______________________________________________ >>>>>>>>>> Do not post admin requests to the list. They will be ignored. >>>>>>>>>> Webobjects-dev mailing list (Webobjects-dev@lists.apple.com >>>>>>>>>> <mailto:Webobjects-dev@lists.apple.com>) >>>>>>>>>> Help/Unsubscribe/Update your Subscription: >>>>>>>>>> https://lists.apple.com/mailman/options/webobjects-dev/aaron%40chatnbike.com >>>>>>>>>> >>>>>>>>>> <https://lists.apple.com/mailman/options/webobjects-dev/aaron%40chatnbike.com> >>>>>>>>>> >>>>>>>>>> This email sent to aa...@chatnbike.com <mailto:aa...@chatnbike.com> >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> Do not post admin requests to the list. They will be ignored. >>>>>>>>> Webobjects-dev mailing list (Webobjects-dev@lists.apple.com >>>>>>>>> <mailto:Webobjects-dev@lists.apple.com>) >>>>>>>>> Help/Unsubscribe/Update your Subscription: >>>>>>>>> https://lists.apple.com/mailman/options/webobjects-dev/samuel%40samkar.com >>>>>>>>> >>>>>>>>> <https://lists.apple.com/mailman/options/webobjects-dev/samuel%40samkar.com> >>>>>>>>> >>>>>>>>> This email sent to sam...@samkar.com <mailto:sam...@samkar.com> >>>>>>> >>>>>> >>>>> >>>> >>>> _______________________________________________ >>>> Do not post admin requests to the list. They will be ignored. >>>> Webobjects-dev mailing list (Webobjects-dev@lists.apple.com >>>> <mailto:Webobjects-dev@lists.apple.com>) >>>> Help/Unsubscribe/Update your Subscription: >>>> https://lists.apple.com/mailman/options/webobjects-dev/tim%40triptera.com.au >>>> >>>> <https://lists.apple.com/mailman/options/webobjects-dev/tim%40triptera.com.au> >>>> >>>> This email sent to t...@triptera.com.au <mailto:t...@triptera.com.au> >>> >> >
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
