[WICKET-7179] add support for jQuery 4.0.0 by reiern70 · Pull Request #1412 · apache/wicket

reiern70 · 2026-03-31T19:59:43Z

No description provided.

martin-g · 2026-03-31T20:15:12Z

I can't believe that there is no need of any migrations in wicket-jquery-ajax.js !
The migration guide is rather long - https://jquery.com/upgrade-guide/4.0/. I'd expect something to break but the JS tests pass!

@reiern70 You may want to add jquery-migrate-4.0.2.js next to jquery.js and see whether it reports something.
I think it would be a good idea to contribute it together with jquery.js until Wicket 11.0.0 is about to be released.

martin-g · 2026-03-31T20:18:13Z

 		return INSTANCE_3;
 	}

+	public static JQueryResourceReference getV4()


I should have checked the diff before my comment!
The V4 is not in use yet! This is the reason why the tests pass.

See

https://blog.jqueryui.com/2026/01/jquery-ui-1-14-2-released/

The new release seems to be compatible with 4.0

This link is relevant to wicket-jquery-ui and wiquery but it does not affect wicket-core anyhow.

I know. This is just a heads up tha we need to update the related wicket-stuff projects too. It seems this new release is also compatible with jQuery 4

reiern70 · 2026-04-01T14:43:56Z

I will enable it and see what fails

reiern70 · 2026-04-10T17:37:18Z

@martin-g test are green locally

martin-g · 2026-04-13T11:23:28Z

@reiern70 You need to use mvn ... -Pjs-test profile to run the JavaScript unit tests.

reiern70 · 2026-04-13T14:54:21Z

@reiern70 You need to use mvn ... -Pjs-test profile to run the JavaScript unit tests.

Thanks for the info

reiern70 · 2026-04-13T16:46:09Z

@reiern70 You need to use mvn ... -Pjs-test profile to run the JavaScript unit tests.

I can't run them locally...

martin-g · 2026-04-13T19:54:49Z

What is the error ?

You can also start them via Jetty with https://github.com/apache/wicket/blob/master/testing/wicket-js-tests/src/test/java/org/apache/wicket/testing/jstest/StartJavaScriptTests.java#L41

Then you can execute them in a browser with http://localhost:8080/ajax-tests/test/js/all.html?4.0.0

reiern70 · 2026-04-15T14:58:11Z

What is the error ?

You can also start them via Jetty with https://github.com/apache/wicket/blob/master/testing/wicket-js-tests/src/test/java/org/apache/wicket/testing/jstest/StartJavaScriptTests.java#L41

Then you can execute them in a browser with http://localhost:8080/ajax-tests/test/js/all.html?4.0.0

Not able to run test in sandbox mode.

reiern70 · 2026-04-17T16:42:24Z

What is the error ?
You can also start them via Jetty with https://github.com/apache/wicket/blob/master/testing/wicket-js-tests/src/test/java/org/apache/wicket/testing/jstest/StartJavaScriptTests.java#L41
Then you can execute them in a browser with http://localhost:8080/ajax-tests/test/js/all.html?4.0.0

Not able to run test in sandbox mode.

@martin-g I have fixed JavaScript tests

reiern70 · 2026-04-17T16:54:55Z

What is the error ?
You can also start them via Jetty with https://github.com/apache/wicket/blob/master/testing/wicket-js-tests/src/test/java/org/apache/wicket/testing/jstest/StartJavaScriptTests.java#L41
Then you can execute them in a browser with http://localhost:8080/ajax-tests/test/js/all.html?4.0.0

Not able to run test in sandbox mode.

@martin-g I have fixed JavaScript tests

https://github.com/apache/wicket/actions/runs/24576240090/job/71862191241#step:8:4355 no idea how to fix this. @martin-g ?

Signed-off-by: Martin Tzvetanov Grigorov <mgrigorov@apache.org>

…andbox Otherwise it looks for CI env var to set --no-sandbox Signed-off-by: Martin Tzvetanov Grigorov <mgrigorov@apache.org>

Signed-off-by: Martin Tzvetanov Grigorov <mgrigorov@apache.org>

martin-g · 2026-04-18T03:35:00Z

@reiern70 See my commits. Now the error is more clear - [INFO] .Test "non-wicket response." took longer than 3000ms. You need to debug

wicket/wicket-core/src/test/js/ajax.js

Line 206 in ddf0f6d

test('non-wicket response.', assert => {

and see why it does not work.

reiern70 · 2026-04-18T15:07:24Z

All tests passed locally and pur application seems to work fine with a copy of jquery AJAX.... js file. Regards - Ernesto Reinaldo Barreiro Apache Wicket Committer

…

On Fri, Apr 17, 2026, 10:35 PM Martin Grigorov ***@***.***> wrote: *martin-g* left a comment (apache/wicket#1412) <#1412?email_source=notifications&email_token=AADQ6PZ4EZ5CS3T4WLJMH6D4WLZXTA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMRXGI2TOMZSGA22M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJNLQOJPWG33NNVSW45C7N5YGK3S7MNWGSY3L#issuecomment-4272573205> @reiern70 <https://github.com/reiern70> See my commits. Now the error is more clear - [INFO] .Test "non-wicket response." took longer than 3000ms. You need to debug https://github.com/apache/wicket/blob/ddf0f6da30b237296188bda7bd570b4612356aa4/wicket-core/src/test/js/ajax.js#L206 and see why it does not work. — Reply to this email directly, view it on GitHub <#1412?email_source=notifications&email_token=AADQ6PZ4EZ5CS3T4WLJMH6D4WLZXTA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMRXGI2TOMZSGA22M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJNLQOJPWG33NNVSW45C7N5YGK3S7MNWGSY3L#issuecomment-4272573205>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AADQ6P5DG5MOX2NBOB2FE234WLZXTAVCNFSM6AAAAACXIHYNU2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DENZSGU3TGMRQGU> . You are receiving this because you were mentioned.Message ID: ***@***.***>

martin-g · 2026-04-18T20:42:32Z

Here the JS tests fail the same way as at CI

reiern70 · 2026-04-20T18:33:21Z

Here the JS tests fail the same way as at CI

martin-g · 2026-04-20T19:04:50Z

75 out of 109 have passed for you and then non-wicket response hangs. Same issue as at CI.

reiern70 · 2026-04-21T18:51:29Z

@martin-g I have fixed JS tests. But I can't still do a full build

Running "qunit:amd" (qunit) task [INFO] >> There was an error with headless chrome [INFO] Fatal error: Failed to launch the browser process: Code: null [INFO] [INFO] stderr: [INFO] [211268:211268:0421/132941.299328:FATAL:content/browser/zygote_host/zygote_host_impl_linux.cc:128] No usable sandbox! If you are running on Ubuntu 23.10+ or another Linux distro that has disabled unprivileged user namespaces with AppArmor, see https://chromium.googlesource.com/chromium/src/+/main/docs/security/apparmor-userns-restrictions.md. Otherwise see https://chromium.googlesource.com/chromium/src/+/main/docs/linux/suid_sandbox_development.md for more information on developing with the (older) SUID sandbox. If you want to live dangerously and need an immediate workaround, you can try using --no-sandbox. [INFO] Received signal 6 [INFO] #0 0x5e82b33aedea (/home/reiern70/.cache/puppeteer/chrome/linux-147.0.7727.56/chrome-linux64/chrome+0x4a69de9) [INFO] #1 0x5e82b9199d84 (/home/reiern70/.cache/puppeteer/chrome/linux-147.0.7727.56/chrome-linux64/chrome+0xa854d83) [INFO] #2 0x72492c845330 (/usr/lib/x86_64-linux-gnu/libc.so.6+0x4532f) [INFO] #3 0x72492c84527e (/usr/lib/x86_64-linux-gnu/libc.so.6+0x4527d) [INFO] #4 0x72492c8288ff (/usr/lib/x86_64-linux-gnu/libc.so.6+0x288fe) [INFO] #5 0x5e82b9190cf5 (/home/reiern70/.cache/puppeteer/chrome/linux-147.0.7727.56/chrome-linux64/chrome+0xa84bcf4) [INFO] #6 0x5e82b914ff4d (/home/reiern70/.cache/puppeteer/chrome/linux-147.0.7727.56/chrome-linux64/chrome+0xa80af4c) [INFO] #7 0x5e82b914fead (/home/reiern70/.cache/puppeteer/chrome/linux-147.0.7727.56/chrome-linux64/chrome+0xa80aeac) [INFO] #8 0x5e82b490edde (/home/reiern70/.cache/puppeteer/chrome/linux-147.0.7727.56/chrome-linux64/chrome+0x5fc9ddd) [INFO] #9 0x5e82b37ce7f9 (/home/reiern70/.cache/puppeteer/chrome/linux-147.0.7727.56/chrome-linux64/chrome+0x4e897f8) [INFO] #10 0x5e82b4657c4b (/home/reiern70/.cache/puppeteer/chrome/linux-147.0.7727.56/chrome-linux64/chrome+0x5d12c4a) [INFO] #11 0x5e82b849cbc7 (/home/reiern70/.cache/puppeteer/chrome/linux-147.0.7727.56/chrome-linux64/chrome+0x9b57bc6) [INFO] #12 0x5e82b465281c (/home/reiern70/.cache/puppeteer/chrome/linux-147.0.7727.56/chrome-linux64/chrome+0x5d0d81b) [INFO] #13 0x5e82b383f30f (/home/reiern70/.cache/puppeteer/chrome/linux-147.0.7727.56/chrome-linux64/chrome+0x4efa30e) [INFO] #14 0x72492c82a1ca (/usr/lib/x86_64-linux-gnu/libc.so.6+0x2a1c9) [INFO] #15 0x72492c82a28b (/usr/lib/x86_64-linux-gnu/libc.so.6+0x2a28a) [INFO] #16 0x5e82b505430a (/home/reiern70/.cache/puppeteer/chrome/linux-147.0.7727.56/chrome-linux64/chrome+0x670f309) [INFO] r8: 000023680013c267 r9: 0000000000000001 r10: 0000000000000008 r11: 0000000000000246 [INFO] r12: 0000000000000006 r13: 0000000000000268 r14: 0000000000000016 r15: 00007ffe964ed918 [INFO] di: 0000000000033944 si: 0000000000033944 bp: 00007ffe964ed280 bx: 0000000000033944 [INFO] dx: 0000000000000006 ax: 0000000000000000 cx: 000072492c89eb2c sp: 00007ffe964ed240 [INFO] ip: 000072492c89eb2c efl: 0000000000000246 cgf: 002b000000000033 erf: 0000000000000004 [INFO] trp: 000000000000000e msk: 0000000000000000 cr2: 0000000000000038 [INFO] [end of stack trace]

martin-g · 2026-04-21T19:15:15Z

00ee8b9 should tell Puppeteer to start Chrome without sandbox.
Another way to tell Puppeteer to start in headless mode without sandbox is by export CI=true

reiern70 · 2026-04-22T14:31:16Z

export CI=true

With this build blocks at some point

reiern70 · 2026-04-22T14:41:26Z

export CI=true

With this build blocks at some point

>> 109 tests completed in 4336ms, with 0 failed, 0 skipped, and 0 todo.
[INFO] 
[INFO] Running "qunit:amd" (qunit) task
[INFO] Testing http://localhost:38887/test/js/amd.html?4.0.0 GET /test/js/amd.html?4.0.0 200 0.597 ms - 1200
[INFO] GET /test/js/qunit/qunit.css 200 0.577 ms - 9726
[INFO] GET /test/js/amd/require.js 200 0.677 ms - 15825
[INFO] 
[INFO] >> ReferenceError: QUnit is not defined
[INFO] >>     at <anonymous> (:164:3)
[INFO] >>     at <anonymous> (:282:2)
[INFO] GET /favicon.ico 404 0.308 ms - 150
[INFO] Failed to load resource: the server responded with a status of 404 (Not Found)
[INFO] GET /test/js/amd.js 200 1.083 ms - 2726
[INFO] GET /test/js/qunit/qunit.js 200 1.179 ms - 279675
[INFO] GET /main/java/org/apache/wicket/resource/jquery/jquery-4.0.0.js 200 0.553 ms - 255967
[INFO] GET /main/java/org/apache/wicket/ajax/res/js/wicket-ajax-jquery.js 200 0.576 ms - 73390

reiern70 · 2026-04-22T14:44:30Z

export CI=true

With this build blocks at some point

>> 109 tests completed in 4336ms, with 0 failed, 0 skipped, and 0 todo.
[INFO] 
[INFO] Running "qunit:amd" (qunit) task
[INFO] Testing http://localhost:38887/test/js/amd.html?4.0.0 GET /test/js/amd.html?4.0.0 200 0.597 ms - 1200
[INFO] GET /test/js/qunit/qunit.css 200 0.577 ms - 9726
[INFO] GET /test/js/amd/require.js 200 0.677 ms - 15825
[INFO] 
[INFO] >> ReferenceError: QUnit is not defined
[INFO] >>     at <anonymous> (:164:3)
[INFO] >>     at <anonymous> (:282:2)
[INFO] GET /favicon.ico 404 0.308 ms - 150
[INFO] Failed to load resource: the server responded with a status of 404 (Not Found)
[INFO] GET /test/js/amd.js 200 1.083 ms - 2726
[INFO] GET /test/js/qunit/qunit.js 200 1.179 ms - 279675
[INFO] GET /main/java/org/apache/wicket/resource/jquery/jquery-4.0.0.js 200 0.553 ms - 255967
[INFO] GET /main/java/org/apache/wicket/ajax/res/js/wicket-ajax-jquery.js 200 0.576 ms - 73390

export CI=true

With this build blocks at some point

>> 109 tests completed in 4336ms, with 0 failed, 0 skipped, and 0 todo.
[INFO] 
[INFO] Running "qunit:amd" (qunit) task
[INFO] Testing http://localhost:38887/test/js/amd.html?4.0.0 GET /test/js/amd.html?4.0.0 200 0.597 ms - 1200
[INFO] GET /test/js/qunit/qunit.css 200 0.577 ms - 9726
[INFO] GET /test/js/amd/require.js 200 0.677 ms - 15825
[INFO] 
[INFO] >> ReferenceError: QUnit is not defined
[INFO] >>     at <anonymous> (:164:3)
[INFO] >>     at <anonymous> (:282:2)
[INFO] GET /favicon.ico 404 0.308 ms - 150
[INFO] Failed to load resource: the server responded with a status of 404 (Not Found)
[INFO] GET /test/js/amd.js 200 1.083 ms - 2726
[INFO] GET /test/js/qunit/qunit.js 200 1.179 ms - 279675
[INFO] GET /main/java/org/apache/wicket/resource/jquery/jquery-4.0.0.js 200 0.553 ms - 255967
[INFO] GET /main/java/org/apache/wicket/ajax/res/js/wicket-ajax-jquery.js 200 0.576 ms - 73390

export CI=true

With this build blocks at some point

>> 109 tests completed in 4336ms, with 0 failed, 0 skipped, and 0 todo.
[INFO] 
[INFO] Running "qunit:amd" (qunit) task
[INFO] Testing http://localhost:38887/test/js/amd.html?4.0.0 GET /test/js/amd.html?4.0.0 200 0.597 ms - 1200
[INFO] GET /test/js/qunit/qunit.css 200 0.577 ms - 9726
[INFO] GET /test/js/amd/require.js 200 0.677 ms - 15825
[INFO] 
[INFO] >> ReferenceError: QUnit is not defined
[INFO] >>     at <anonymous> (:164:3)
[INFO] >>     at <anonymous> (:282:2)
[INFO] GET /favicon.ico 404 0.308 ms - 150
[INFO] Failed to load resource: the server responded with a status of 404 (Not Found)
[INFO] GET /test/js/amd.js 200 1.083 ms - 2726
[INFO] GET /test/js/qunit/qunit.js 200 1.179 ms - 279675
[INFO] GET /main/java/org/apache/wicket/resource/jquery/jquery-4.0.0.js 200 0.553 ms - 255967
[INFO] GET /main/java/org/apache/wicket/ajax/res/js/wicket-ajax-jquery.js 200 0.576 ms - 73390

The same as in here

https://github.com/apache/wicket/actions/runs/24739332723/job/72374517805?pr=1412

reiern70 · 2026-04-23T19:51:18Z

@martin-g I might need your help fixing amd.js test when run from maven. Test pass if run from normal browser

martin-g · 2026-04-23T19:53:24Z

we can drop amd.js. No one cares about AMD these days

reiern70 · 2026-04-23T20:20:45Z

we can drop amd.js. No one cares about AMD these days

Done. Build passes locally.

martin-g · 2026-04-23T20:40:21Z

We can update it to 2.7.0 from https://github.com/jakerella/jquery-mockjax/blob/master/dist/jquery.mockjax.js

martin-g · 2026-04-23T20:43:00Z


 		queryString = jQuery.param(queryString, true);
-		var space = jQuery.fn.jquery.indexOf("3") === 0 ? "%20" : "+";
+		var space = jQuery.fn.jquery.indexOf("4") === 0 ? "%20" : "+";


This should be: if version.startsWith('2') ? "+" : "%20"

If I put 2 tests fail

The idea is that the JS tests could be reused to test with any version of jQuery.

http://localhost:8080/ajax-tests/test/js/all.html?4.0.0 will test with jQuery 4.0.0
http://localhost:8080/ajax-tests/test/js/all.html?3.7.1 will test with jQuery 3.7.1

AFAIR var space = jQuery.fn.jquery.indexOf("4") === 0 ? "%20" : "+"; is checking which major version of jQuery is in use. Both 4.x and 3.x should use %20 as a space in urls.

martin-g · 2026-04-23T20:43:14Z


 		queryString = jQuery.param(queryString, true);
-		var space = jQuery.fn.jquery.indexOf("3") === 0 ? "%20" : "+";
+		var space = jQuery.fn.jquery.indexOf("4") === 0 ? "%20" : "+";


…rateResourceReference.java Co-authored-by: Martin Grigorov <martin-g@users.noreply.github.com>

…-ajax-jquery.js Co-authored-by: Martin Grigorov <martin-g@users.noreply.github.com>

…f jquery.mockjax.js

reiern70 · 2026-04-24T18:21:07Z

Build is green locally

Including JavaScript tests

martin-g · 2026-04-27T06:19:30Z

+/**
+ * The jQuery migrate library
+ */
+public class JQueryMigrateResourceReference extends JavaScriptResourceReference


I am not sure whether this class should stay.
jquery-migrate.js is a helper that should be used while migrating jQuery dependant code from 3.x to 4.x. But once the migration is done it is not needed anymore.

It does not do any harm though.

I am not sure whether this class should stay. jquery-migrate.js is a helper that should be used while migrating jQuery dependant code from 3.x to 4.x. But once the migration is done it is not needed anymore.

It does not do any harm though.

It is needed by applications wanting to migrate. I.e. I have used it to migrate our app to jQuery 4,0 and updated wicket jQuery AJAX file

martin-g · 2026-04-27T06:19:44Z

 jQuery(document).ready(function() {
 	"use strict";

+    var isWindow = function (obj) { return obj != null && obj === obj.window; };


Suggested change

var isWindow = function (obj) { return obj != null && obj === obj.window; };

…f jquery.mockjax.js

ernestosemedy · 2026-04-27T15:43:52Z

@martin-g

Again green build locally. I have addressed your comments

martin-g

Great work, @reiern70 !

reiern70 requested a review from martin-g March 31, 2026 19:59

martin-g reviewed Mar 31, 2026

View reviewed changes

reiern70 force-pushed the reiern70/WICKET-7179 branch from 4c50e0c to c06b954 Compare April 10, 2026 17:03

martin-g reviewed Apr 13, 2026

View reviewed changes

Comment thread wicket-core/src/main/java/org/apache/wicket/ajax/res/js/wicket-ajax-jquery.js Outdated

Comment thread wicket-core/src/main/java/org/apache/wicket/ajax/res/js/wicket-ajax-jquery.js Outdated

[WICKET-7179] add support for jQuery 4.0.0

1a2aac8

reiern70 force-pushed the reiern70/WICKET-7179 branch from c4d7dc8 to 1a2aac8 Compare April 17, 2026 16:46

martin-g added 6 commits April 18, 2026 05:55

Update QUnit from 2.19.4 to 2.25.0

663f321

Signed-off-by: Martin Tzvetanov Grigorov <mgrigorov@apache.org>

Update Node.js to v24.15.0 and npm to v11.12.1

2485aaf

Signed-off-by: Martin Tzvetanov Grigorov <mgrigorov@apache.org>

Test with jQuery v4.0.0

3b967c2

Signed-off-by: Martin Tzvetanov Grigorov <mgrigorov@apache.org>

COnfigure Puppeteer to always start Chrome in headless mode with no s…

00ee8b9

…andbox Otherwise it looks for CI env var to set --no-sandbox Signed-off-by: Martin Tzvetanov Grigorov <mgrigorov@apache.org>

Update Grunt to v1.6.2 and grunt-contrib-qunit to v 10.2.0

b4433b2

Signed-off-by: Martin Tzvetanov Grigorov <mgrigorov@apache.org>

Merge branch 'master' into reiern70/WICKET-7179

3ee81e7

Signed-off-by: Martin Tzvetanov Grigorov <mgrigorov@apache.org>

reiern70 added 3 commits April 21, 2026 12:30

[WICKET-7179] fix JS tests

379895a

[WICKET-7179] fix JS tests

8d5db51

[WICKET-7179] fix JS tests

d6944fd

reiern70 added 2 commits April 21, 2026 13:13

[WICKET-7179] fix JS tests

fa2c782

[WICKET-7179] fix JS tests

5f5df6c

[WICKET-7179] get rid of AMD

63b5fba

martin-g reviewed Apr 23, 2026

View reviewed changes

reiern70 and others added 3 commits April 24, 2026 10:41

Update wicket-core/src/main/java/org/apache/wicket/resource/JQueryMig…

065032e

…rateResourceReference.java Co-authored-by: Martin Grigorov <martin-g@users.noreply.github.com>

Update wicket-core/src/main/java/org/apache/wicket/ajax/res/js/wicket…

74ec860

…-ajax-jquery.js Co-authored-by: Martin Grigorov <martin-g@users.noreply.github.com>

[WICKET-7179] include feedback + fix Wicket.isWindow + bump version o…

9f9e0d6

…f jquery.mockjax.js

reiern70 requested a review from martin-g April 24, 2026 18:21

martin-g reviewed Apr 27, 2026

View reviewed changes

[WICKET-7179] include feedback + fix Wicket.isWindow + bump version o…

5047621

…f jquery.mockjax.js

reiern70 requested a review from martin-g April 27, 2026 17:59

martin-g approved these changes Apr 27, 2026

View reviewed changes

Conversation

reiern70 commented Mar 31, 2026

Uh oh!

martin-g commented Mar 31, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

reiern70 commented Apr 1, 2026

Uh oh!

reiern70 commented Apr 10, 2026

Uh oh!

Uh oh!

Uh oh!

martin-g commented Apr 13, 2026

Uh oh!

reiern70 commented Apr 13, 2026

Uh oh!

reiern70 commented Apr 13, 2026

Uh oh!

martin-g commented Apr 13, 2026

Uh oh!

reiern70 commented Apr 15, 2026

Uh oh!

reiern70 commented Apr 17, 2026

Uh oh!

reiern70 commented Apr 17, 2026

Uh oh!

martin-g commented Apr 18, 2026

Uh oh!

reiern70 commented Apr 18, 2026 via email

Uh oh!

martin-g commented Apr 18, 2026

Uh oh!

reiern70 commented Apr 20, 2026

Uh oh!

martin-g commented Apr 20, 2026

Uh oh!

reiern70 commented Apr 21, 2026

Uh oh!

martin-g commented Apr 21, 2026

Uh oh!

reiern70 commented Apr 22, 2026

Uh oh!

reiern70 commented Apr 22, 2026

Uh oh!

reiern70 commented Apr 22, 2026

Uh oh!

reiern70 commented Apr 23, 2026

Uh oh!

martin-g commented Apr 23, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

reiern70 commented Apr 23, 2026

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

martin-g commented Mar 31, 2026 •

edited

Loading

martin-g commented Apr 23, 2026 •

edited

Loading