Re: prototype.js
Re: prototype.js
- Subject: Re: prototype.js
- From: Fredrik Lindgren via Webobjects-dev <email@hidden>
- Date: Thu, 14 Aug 2025 11:36:25 +0200
If you are willing to share how you "turn it off", it would be nice to try!
/Fredrik
> 13 aug. 2025 kl. 16:54 skrev Jesse Tayler <email@hidden>:
>
> 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 unified JS which was
> intentionally weirdly different on all browsers and honestly, you could not
> get anything done before prototype!
>
>
>
>> On Aug 13, 2025, at 7:55 AM, Fredrik Lindgren via Webobjects-dev
>> <email@hidden> wrote:
>>
>> 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.
>>
>> There is a framework that might be used to replace the Ajax komponents, that
>> is called htmx (https://htmx.org/). That might be a path forward, but to get
>> the same level of integration as Ajax, there is a lot of work.
>>
>> I can probably use the AjaxUtils.ajaxComponentActionUrl(WOContext) to get
>> the html that should replace a similar update container.
>>
>> Has anyone tried this approach?
>>
>> /Fredrik
>>
>>
>>> 13 aug. 2025 kl. 10:30 skrev Daniele Corti <email@hidden>:
>>>
>>> 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 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
>>> D.
>>>
>>> Il Mer 13 Ago 2025, 09:43 Fredrik Lindgren via Webobjects-dev
>>> <email@hidden <mailto:email@hidden>> 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
>>>> _______________________________________________
>>>> Do not post admin requests to the list. They will be ignored.
>>>> Webobjects-dev mailing list (email@hidden
>>>> <mailto:email@hidden>)
>>>> Help/Unsubscribe/Update your Subscription:
>>>>
>>>> This email sent to email@hidden <mailto:email@hidden>
>>
>> _______________________________________________
>> Do not post admin requests to the list. They will be ignored.
>> Webobjects-dev mailing list (email@hidden)
>> Help/Unsubscribe/Update your Subscription:
>>
>> This email sent to email@hidden
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
| References: | |
| | >prototype.js (From: Fredrik Lindgren via Webobjects-dev <email@hidden>) |
| | >Re: prototype.js (From: Daniele Corti via Webobjects-dev <email@hidden>) |
| | >Re: prototype.js (From: Fredrik Lindgren via Webobjects-dev <email@hidden>) |
| | >Re: prototype.js (From: Jesse Tayler via Webobjects-dev <email@hidden>) |