Task checkbox state is reset after page refresh in Chromium-based browsers and page hard refersh in Firefox browser

[petrenkonikita112263]

Describe the bug
Toggling a task checkbox correctly updates the task status (e.g. To Do → Done or Done → In Progress). However, after refreshing the page in Chromium-based browsers (MS Edge or GG), the checkbox is rendered as unchecked, even though the underlying task status has been updated.

Steps to reproduce

1. Install latest Task Manager (on reported date of issue - v3.11.2)
2. Obtain trial license
3. From Task home page TaskManager.WebHome create any task with status ToDo
4. Display such task in Sandbox page using wiki syntax {{task reference="TaskManager.Test Task Checkbox Functionality" status="ToDo" reporter="XWiki.Admin"/}}
5. In the view mode toggle checkbox, notice the pop-up window with information about the successful update of the task, and also the changes in the history revision on the task page, additionaly the task now has a date of completedDate and a status of Done with 100% progress.
6. Refresh test page

Expected behavior
The checkbox remains in the state selected by the user after the page is refreshed, reflecting the current task status.

Actual behavior
After refreshing the page, the checkbox is displayed as unchecked, although the task status was successfully updated. The visual state of the checkbox is therefore inconsistent with the actual task status.

Environment:

• OS: Ubuntu 26.04
• Browser: edge
• XWiki version: 15.10
• App version: 3.11.2

Additional context
This issue doesn't occur in Firefox browser. See confirmation of issue regarding Firefox in this comment.

On my end, in browser console I have nothing that could hint the cause of the issue, the XWiki logs contain only these lines whenever I'm toggeling the checkbox

2026-08-05 14:57:47,093 [qtp592688102-124 - http://localhost:8080/xwiki/rest/wikis/xwiki/spaces/TaskManager/pages/Test%20Task%20Checkbox%20Functionality/task?status=toggle] WARN  o.h.e.j.s.SqlExceptionHelper   - SQL Warning Code: -1100, SQLState: 02000 
2026-08-05 14:57:47,094 [qtp592688102-124 - http://localhost:8080/xwiki/rest/wikis/xwiki/spaces/TaskManager/pages/Test%20Task%20Checkbox%20Functionality/task?status=toggle] WARN  o.h.e.j.s.SqlExceptionHelper   - no data 

[trrenty]

Hello. The task macro shouldnt really be used like this. When a task macro gets inserted in the page, it forms a relation with the task page mentioned in the reference parameter. For this relation to exist, the reference needs to point to a location that doesnt exist yet and will be created automatically by the application. This relation is created through the owner/location field of the task page. It is managed by the app and viewable only through the object editor.

When the task checkbox is pressed, the task page is updated successfully because the reference is correct. However, after the change is made, the macro can't be updated because the current page is not the owner of the task page. The task page was created through the TaskManager homepage instead of being created by the task macro.

If the user wants to have a view of some task page as if they used the task macro, they can use the tasks macro. This will render the task similarly to the task macro. The checkbox would still work but the task wont be editable through the wysiwyg editor, only through the task page.

A fix for this issue would be to not allow the users to input task references in the task macro. Currently, the reference is generate automatically but it can still be edited. To discourage it, we could also disable the input or even hide it if the generation was successful. WDYT? @snazare @abrassat

[petrenkonikita112263]

What if a user has ended with such a task as a result of a Confluence migration because in migrator you have an advanced configuration that migrate all actions items to checkboxes in XWiki, and this creates a lot of tasks in the Task Manager.

[trrenty]

it shouldnt be possible to result in such a state after a confluence migration. The migrator converts the confluence action items into task macros with populated task references. Then, the migrated page containing various task macros will get saved which results in the creation of the task pages identified by the references

[petrenkonikita112263]

Okay, but the problem will still be there, migrated page will contain checkbox depending on task status, it will be either checked or unchecked, and toggling this checkbox in chromium browser will not preserve the state after browser refresh.

[trrenty]

Another note: the issue reproduces on all browsers. Refreshing the page on firefox preserves the state of the input by some caching mechanism. Refreshing the page with ctrl + f5 will cause the issue as well