Branch: refs/heads/XWIKI-6688-vitest Home: https://github.com/xwiki/xwiki-platform Commit: 29f28fe13d351706bf09381626407397ed67d4c9 https://github.com/xwiki/xwiki-platform/commit/29f28fe13d351706bf09381626407... Author: Vincent Massol <[email protected]> Date: 2026-09-17 (Thu, 17 Sep 2026) Changed paths: M pnpm-lock.yaml M pnpm-workspace.yaml M xwiki-platform-core/xwiki-platform-flamingo/xwiki-platform-flamingo-skin/xwiki-platform-flamingo-skin-test/xwiki-platform-flamingo-skin-test-docker/src/test/it/org/xwiki/flamingo/test/docker/DocExtraTabsIT.java M xwiki-platform-core/xwiki-platform-web/xwiki-platform-web-war/pom.xml A xwiki-platform-core/xwiki-platform-web/xwiki-platform-web-war/src/test/node/package.json A xwiki-platform-core/xwiki-platform-web/xwiki-platform-web-war/src/test/node/xwiki.test.js Log Message: ----------- XWIKI-6688: Possible race condition when clicking on a tab at the bottom of a page in view mode * Replace the functional test that opens a document extra pane while another one is still loading with a JavaScript unit test, which decides in which order the panes are loaded instead of needing a pane that is slow on purpose, and which runs in about a second instead of several minutes. It also pins the two parts of the fix separately, which the functional test cannot do: without the guard the pane requested first is displayed, and displaying it drops the "empty" marker as a side effect, hiding the fact that the marker isn't dropped otherwise. * Run the JavaScript unit tests of xwiki-platform-web-war with vitest, from a node package located in src/test/node. Prototype isn't published on npm, so the Maven build extracts it from the webjar that this module already depends on in test scope. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]> To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-platform/settings/notifications