Upcoming jQuery upgrade: your thoughts about extension compatibility

[Antonin Delpeuch (lists)]

Hello all,

For a long time we have been willing to upgrade the jQuery library that
we use for OpenRefine's frontend from its current, end-of-life version
(1.12.4) to a newer version. This is work that was started by Tom Morris
and that GitHub user elebitzero picked up lately. There are various
reasons why it makes sense to do that: jQuery v1 has known
vulnerabilities, and v3 (that we are migrating to) takes advantage of
the newer (and more unified) browser APIs, if I understand correctly.

Now we are ready to flip the switch. The only thing is: this can
potentially break extensions which use some deprecated jQuery syntax in
their own code. Therefore we turn to the dev community and want to ask:
can we release this change in OpenRefine 3.6, or do you see a better way
to do this?

OpenRefine 3.5 already includes the jQuery migrate library, which should
generate warnings when your extension uses deprecated jQuery constructs.
That should hopefully help to identify any outstanding calls.

Overall, jQuery has been quite conservative in its changes, and has kept
deprecated syntax working for a very long time, so it should not be a
ton of work to migrate an extension.

Looking forward to your feedback,

Antonin

[Thad Guidry]

Hi Marek,

I personally would like to know your feelings about our plans below for the jQuery upgrade in OpenRefine, since FAIRDataTeam extension is still used by several teams globally.

Thad

https://www.linkedin.com/in/thadguidry/

https://calendly.com/thadguidry/

--
You received this message because you are subscribed to the Google Groups "OpenRefine Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openrefine-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openrefine-dev/34d8654d-fcc9-2b0f-646b-273f5ffd890f%40antonin.delpeuch.eu.