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 Ajax framework.
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 s
I've started some work on partial rendering/Ajax functionality for my
ng-objects project. Since I want some template-level compatibility between WO
and NG, my current plan involves eventually backporting some of the (plain JS)
client side stuff to WO, at least for some baseline functionality/ele
I also have had this problem —
I have a weird hack fix that does SOME of the conflicts, but I also have a hack
to basically “turn it off”
I would LOVE to move to AJAX that has JQuery vs. prototype which conflicts and
isn’t really used anymore—
Sad because prototype was an amazing idea! It unif
Yes, we are using that feature in jQuery. However it seems that prototype is
overriding some features in native javascript that Quill uses (and other
libraries). This brakes those libraries.
Ideal would be to update the Ajax-classes to not use prototype, but I realise
this is a major effort.
Hi,
A while ago, I did a project using Ajax framewotk, with Bootstrap, using
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 was able to get both the Aja
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 li
