Re: Upgrading to jQuery 3.5.1

Hello!

On Thu, Jul 14, 2022 at 2:17 PM Volker Lamp <[email protected]> wrote:

> I agree. How about -- instead of creating a new configuration symbol -- re-using 'tapestry.javascript-infrastructure-provider'? The default value is still 'prototype', by the way, but I intend to change that (see TAP5-2732). Setting it to 'query-migrate' would enable the jQuery Migration Plugin, for both production or development mode.

My idea is similar, but not the same: having a separate
tapestry.javascript-infrastructure-provider value for using latest
jQuery. At my day job, we already had problems with our jQuery code
when upgrading from 1.3 to 1.8 (or 1.12, I don't remember exactly),
and I suppose it's going to be way worse going from 1.x to 3.x.
Tapestry 5 has always been careful about backward compatibility, and I
believe we should keep the existing 'jquery' infrastructure still
using jQuery 1.x. As Ben said, and I agree 100%, "But it should
require a conscious user decision to do so."

Thanks for investigating this!

>
> I'll give it a try and push it to the TAP5-2734 branch when ready.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>


-- 
Thiago