Hi Fredrik, I read a little about Quill, it is modifying DOM with methods like “each” and “inject” which Prototype does too. Since they both do it, they clobber each other and the methods may have the same name but they work differently.
You have a few options: 1) Use Quill inside an iframe so you can avoid conflict with Prototype. You might balk at this thought but consider it a bit. It’s probably the best option you got. 2) While the Ajax Framework is the most common choice, there are others that maybe you could use instead on that page. Maybe the “ERJQueryMobile” framework or perhaps “MooTools” - but it requires learning those. 3) Can you avoid using Ajax on that page? that’s actually the easiest option Trying to rewrite the Ajax 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 > <webobjects-dev@lists.apple.com> 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 with a solution? > > /Fredrik > _______________________________________________ > 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/aaron%40chatnbike.com > > This email sent to aa...@chatnbike.com _______________________________________________ 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
