Re: prototype.js

I dunno- that sounds like a useful trick to me! > On Aug 14, 2025, at 10:02 AM, Mark Gowdy wrote: > > Hi.. > > Dunno if this will help or not, but I added this to my prototype.js file. > It was to tell it to ignore certain elements when you add the element class >

Re: prototype.js

Hi.. Dunno if this will help or not, but I added this to my prototype.js file. It was to tell it to ignore certain elements when you add the element class “noProtoJs” to them You also need the noConflict added somewhere in (order is probably important). The order I use is: * bootstrap.js

Re: prototype.js

ng >>>> jQuery. >>>> >>>> Fortunately, jQuery is distributed with a function called noConflict(), >>>> which is precisely for making jquery work with other javascript libraries. >>>> >>>> Once I found the right call order, I

Re: prototype.js

h the Ajax >>> framework and the jQuery and bootstrap functionality working. >>> >>> I think the only option is to check if there is a way for prorotypes and >>> the other js libraries you use to coexist. >>> >>> Best regards >>>

Re: prototype.js

jquery work with other javascript libraries. >>> >>> Once I found the right call order, I was able to get both the Ajax >>> framework and the jQuery and bootstrap functionality working. >>> >>> I think the only option is to check if there is a way for prorotype

Re: prototype.js

framework to avoid prototype JS can be done… but > it’s not an easy button. > >> On Aug 13, 2025, at 3:43 AM, Fredrik Lindgren via Webobjects-dev >> wrote: >> >> Is there a way to opt out of using prototype.js with the Ajax framework. >> >> We are

Re: prototype.js

For what it’s worth, I had TinyMCE working with the Ajax framework in the past. So if you aren’t married to Quill, maybe use TinyMCE instead. > On Aug 13, 2025, at 3:43 AM, Fredrik Lindgren via Webobjects-dev > wrote: > > Is there a way to opt out of using prototype.js with the Aj

Re: prototype.js

cts-dev > wrote: > > Is there a way to opt out of using prototype.js with the Ajax framework. > > We are having problems integrating for example the quill editor due to > conflicts. > > Anyone have similar problems wit

Re: prototype.js

; I think the only option is to check if there is a way for prorotypes and the >> other js libraries you use to coexist. >> >> Best regards >> D. >> >> Il Mer 13 Ago 2025, 09:43 Fredrik Lindgren via Webobjects-dev >> ha scritto: >> Is there a way to

Re: prototype.js

nd bootstrap functionality working. >> >> I think the only option is to check if there is a way for prorotypes and the >> other js libraries you use to coexist. >> >> Best regards >> D. >> >> Il Mer 13 Ago 2025, 09:43 Fredrik Lindgren via Webobjects-dev

Re: prototype.js

ption is to check if there is a way for prorotypes and the > other js libraries you use to coexist. > > Best regards > D. > > Il Mer 13 Ago 2025, 09:43 Fredrik Lindgren via Webobjects-dev > mailto:webobjects-dev@lists.apple.com>> ha > scritto: >> Is there a

Re: prototype.js

gt; ha scritto: > Is there a way to opt out of using prototype.js with the Ajax framework. > > We are having problems integrating for example the quill editor due to > conflicts. > > Anyone have similar problems with a solution? > > /Fredrik >

prototype.js

Is there a way to opt out of using prototype.js with the Ajax framework. We are having problems integrating for example the quill editor due to conflicts. Anyone have similar problems with a solution? /Fredrik ___ Do not post admin requests to the

Re: WebObjects and prototype.js

Thanks Tim :-) AARON ROSENZWEIG / Chat 'n Bike e: aa...@chatnbike.com t: (301) 956-2319 > On Feb 28, 2019, at 9:31 PM, D Tim Cummings wrote: > > Hi Aaron > > I found a solution. It can be fixed by changing the

Re: WebObjects and prototype.js

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

Re: WebObjects and prototype.js

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

Re: WebObjects and prototype.js

The problem with AjaxAutoComplete depends on how far down you have scrolled the page before typing in the textfield. Simple examples at the top of the page work fine. If you have scrolled down 200px before typing then the drop-down menu will be 200px below the textfield it is related to. Tim >

Re: WebObjects and prototype.js

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

Re: WebObjects and prototype.js

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 autocomple

Re: WebObjects and prototype.js

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 java

Re: WebObjects and prototype.js

Dot you get a console error from javascript? Perhaps the fix is not so complicated. I know that I’ve run into namespace conflicts so severe, I had to abandon almost all of those great cool components using AJAX/prototype and had to kind of re-write that sort of behavior by hand which I was able

Re: WebObjects and prototype.js

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

Re: WebObjects and prototype.js

Hi Everyone especially Samuel! This is what our code looks like: 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 typ

Re: WebObjects and prototype.js

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: Samuel > Le 12 févr. 2019 à 16:26, Aaron Rosenzweig a écrit : > > Hi Everyone, > > We disco

Re: WebObjects and prototype.js

could just pick something. It suddenly stopped showing the autocomplete options without any java errors and without any javascript errors in the browser. It just stopped working. That was with 1.7.3 of Prototype.js — I did not try 1.7.2 — I went directly for 1.7.0 because that is the last

Re: WebObjects and prototype.js

Hi Aaron, what exactly are the problems you encountered? I also have Scriptaculous and Prototype in one project and didn't see anything break yet after the Wonder update. What should we look out for? Maik > Am 12.02.2019 um 22:26 schrieb Aaron Rosenzweig : > > Hi Everyone, > > We discovered

Re: WebObjects and prototype.js

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 Prot

Re: WebObjects and prototype.js

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 :) Michael -- ___ Michael Schmiedgen, BSc Senior Software Engineer Takwa GmbH Friedrich-List-Str. 36 99096 Erfurt GERMANY Tel

Re: WebObjects and prototype.js

> Am 19.01.2019 um 20:46 schrieb Michael Schmiedgen : > > Hi Mark, > >> if upgrading will conflict with Wonder and WebObjects. Has anyone used >> prototype.js 1.7.3 along side with Wonder and WebObjects? Thank you and > > We are using 1.7.3 for years with no kn

Re: WebObjects and prototype.js

Hi Mark, if upgrading will conflict with Wonder and WebObjects. Has anyone used prototype.js 1.7.3 along side with Wonder and WebObjects? Thank you and We are using 1.7.3 for years with no known problems. Michael ___ Do not post admin requests to

Re: WebObjects and prototype.js

e the minified version. To do that go into the Ajax framework and run the script in Support/compress.sh. jw > Am 18.01.2019 um 17:26 schrieb Mark Nguyen : > > Hello everyone! > > We're currently using prototype.js version 1.7.1 along side with Wonder and > WebObjects an

WebObjects and prototype.js

Hello everyone! We're currently using prototype.js version 1.7.1 along side with Wonder and WebObjects and everything is working just fine. However, we're using a script provided by a 3rd party company that imbeds an iframe on our website. We've done various tests and it seems th

Re: Ajax framework and prototype.js 1.7

Jan 6, 2012, at 4:23 AM, Hugi Thordarson wrote: > >> Good morning! >> >> Just wondering if anyone has tried upgrading Ajax framework's prototype.js >> to version 1.7? I'd like to use a plugin that requires the current version, >> specifically, the m

Re: Ajax framework and prototype.js 1.7

and ajax. >>> >>> And this little javascript framework nails some UI features I want to >>> implement. >>> >>> James >>> >>> >>> >>> On Jan 6, 2012, at 5:23 AM, Hugi Thordarson wrote: >>> >>>

Re: Ajax framework and prototype.js 1.7

want to >>> implement. >>> >>> James >>> >>> >>> >>> On Jan 6, 2012, at 5:23 AM, Hugi Thordarson wrote: >>> >>>> Good morning! >>>> >>>> Just wondering if anyone has tried

Re: Ajax framework and prototype.js 1.7

There are actually some pretty extensive selenium tests on the AjaxExample. You could just switch it out and see what breaks. Ramsey On Jan 6, 2012, at 4:23 AM, Hugi Thordarson wrote: > Good morning! > > Just wondering if anyone has tried upgrading Ajax framework's prototype.js

Re: Ajax framework and prototype.js 1.7

at 5:23 AM, Hugi Thordarson wrote: >> >>> Good morning! >>> >>> Just wondering if anyone has tried upgrading Ajax framework's prototype.js >>> to version 1.7? I'd like to use a plugin that requires the current version, >>> specificall

Re: Ajax framework and prototype.js 1.7

ails some UI features I want to > implement. > > James > > > > On Jan 6, 2012, at 5:23 AM, Hugi Thordarson wrote: > >> Good morning! >> >> Just wondering if anyone has tried upgrading Ajax framework's prototype.js >> to version 1.7? I

Re: Ajax framework and prototype.js 1.7

dering if anyone has tried upgrading Ajax framework's prototype.js to > version 1.7? I'd like to use a plugin that requires the current version, > specifically, the most awesome Chosen plugin ( > http://harvesthq.github.com/chosen/ ). > > Cheers, > - hugi ___

Ajax framework and prototype.js 1.7

Good morning! Just wondering if anyone has tried upgrading Ajax framework's prototype.js to version 1.7? I'd like to use a plugin that requires the current version, specifically, the most awesome Chosen plugin ( http://harvesthq.github.com/chosen/ ). Chee