September 2026 - notifications

[xwiki/xwiki-dev-llm] 43cc66: [Misc] State the before/after images rule on the i...
by XWiki Notifications 03 Sep '26

03 Sep '26

Branch: refs/heads/okf-visual-evidence-without-a-pr Home: https://github.com/xwiki/xwiki-dev-llm Commit: 43cc667b27b6bc46770d572825c81f8ffb59e2ce https://github.com/xwiki/xwiki-dev-llm/commit/43cc667b27b6bc46770d572825c81… Author: Vincent Massol <vincent(a)massol.net> Date: 2026-09-03 (Thu, 03 Sep 2026) Changed paths: M xwiki/okf/index.md M xwiki/okf/servers/jira.md M xwiki/skills/xwiki-pull-request/SKILL.md Log Message: ----------- [Misc] State the before/after images rule on the issue, not only on the PR * Move the rule that a visibly changing fix carries before/after images into `okf/servers/jira.md`, next to the how of attaching them. It was stated only as a bullet of the PR template in `xwiki-pull-request`, so it never reached a fix committed straight to `master` — which has no PR body to show the result, and is exactly the case where the images go uncaptured. * Say there that producing the images is also the check that the change works, a test asserting only what it was written to assert. * Shorten the PR-template bullet to the PR-specific half and point it at the OKF for the rule, so the obligation is stated once. * Name it in the `jira` topic line of `okf/index.md`. Co-Authored-By: Claude Opus 5 (1M context) <noreply(a)anthropic.com> To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-dev-llm/settings/notifications

1 0

[xwiki/xwiki-dev-llm] 2b28d5: [Misc] Give server-side rendering its own OKF topic
by XWiki Notifications 03 Sep '26

03 Sep '26

Branch: refs/heads/okf-velocity-generated-wiki-syntax Home: https://github.com/xwiki/xwiki-dev-llm Commit: 2b28d597fe082d9548749960f50cfe3cb146ebd5 https://github.com/xwiki/xwiki-dev-llm/commit/2b28d597fe082d9548749960f50cf… Author: Vincent Massol <vincent(a)massol.net> Date: 2026-09-03 (Thu, 03 Sep 2026) Changed paths: M xwiki/instructions/xwiki-org.md M xwiki/okf/conventions/frontend.md A xwiki/okf/conventions/server-side-rendering.md M xwiki/okf/index.md Log Message: ----------- [Misc] Give server-side rendering its own OKF topic * Add `okf/conventions/server-side-rendering.md`, for code that runs on the server inside a wiki page, sheet or template and produces wiki syntax or HTML. `frontend.md` covers the browser-facing layer — JavaScript, CSS delivery, HTML and WCAG conformance — so a rule about generating wiki syntax is not findable there, whatever its subject matter overlap. * Record in it the blank lines that separate blocks in generated wiki syntax, and the two things that silently remove them: Velocity drops the newline ending a line that ends with a directive, and `$doc.display` on a wiki TextArea returns the rendered field as a single-line `{{html}}` macro with no trailing newline, where the raw property value it replaces was multi-line. A block then joins the paragraph before it, nesting a paragraph or leaving a standalone-only macro such as `{{gallery}}` used inline, which refuses to render. * Cross-link the two files: the accessibility traps for markup emitted from a wiki page stay in `frontend.md`, since they are WCAG conformance rules and splitting them would fragment that topic. * List the topic in `okf/index.md` and name it in the `instructions/xwiki-org.md` mirror. Co-Authored-By: Claude Opus 5 (1M context) <noreply(a)anthropic.com> To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-dev-llm/settings/notifications

1 0

[xwiki-contrib/application-releasenotes] 1e23b3: RN-107: The flow displayer misaligns a change's me...
by XWiki Notifications 03 Sep '26

03 Sep '26

Branch: refs/heads/RN-107 Home: https://github.com/xwiki-contrib/application-releasenotes Commit: 1e23b3b779068f8e2e42656c66012cbf05429d30 https://github.com/xwiki-contrib/application-releasenotes/commit/1e23b3b779… Author: Vincent Massol <vincent(a)massol.net> Date: 2026-09-03 (Thu, 03 Sep 2026) Changed paths: M application-releasenotes-ui/src/main/resources/ReleaseNotes/Code/Change/ChangeDisplayerFlow.xml M application-releasenotes-ui/src/test/java/org/xwiki/releasenotes/DisplayChangesMacroPageTest.java Log Message: ----------- RN-107: The flow displayer misaligns a change's media and displays none when the change has no screenshot * Give every change a media block, the way the grid displayer does: the screenshots when the change has any, its video when it has none, and the "no image" placeholder when it has neither. A change was previously left with an empty half-width column, which made the screenshot of the next change read as illustrating it. * Add a stylesheet to the displayer that starts both halves of a change at the same height: neither column opens with the theme's leading margin any more, and the gallery box hugs its screenshot and pins it to the top instead of padding itself out to a fixed height and centring a short screenshot up to a hundred pixels below the title. The maximised gallery is left alone, so opening a screenshot full screen still fills the viewport. * Cover the two behaviours with page tests: the flow displayer puts the screenshots in the media column and the title in the text column, and both the grid and the flow displayers give a change with no screenshot a media block holding the placeholder. To unsubscribe from these emails, change your notification settings at https://github.com/xwiki-contrib/application-releasenotes/settings/notifica…

1 0

[xwiki/xwiki-dev-llm] ffeeab: [Misc] Document the blank lines that separate bloc...
by XWiki Notifications 03 Sep '26

03 Sep '26

Branch: refs/heads/okf-velocity-generated-wiki-syntax Home: https://github.com/xwiki/xwiki-dev-llm Commit: ffeeab65cbb1033da2e3eea2f8396018c780ed50 https://github.com/xwiki/xwiki-dev-llm/commit/ffeeab65cbb1033da2e3eea2f8396… Author: Vincent Massol <vincent(a)massol.net> Date: 2026-09-03 (Thu, 03 Sep 2026) Changed paths: M xwiki/okf/conventions/frontend.md M xwiki/okf/index.md Log Message: ----------- [Misc] Document the blank lines that separate blocks in generated wiki syntax * Add a "Wiki syntax generated from Velocity" section to `okf/conventions/frontend.md`, whose section on markup emitted from a wiki page is the closest home. Velocity drops the newline ending a line that ends with a directive, and `$doc.display` on a wiki TextArea returns the rendered field as a single-line `{{html}}` macro carrying no trailing newline, so a block a page generates silently joins the paragraph before it — nesting a paragraph inside another, or making a standalone-only macro such as `{{gallery}}` refuse to render at all. * Extend the `frontend` topic line in `okf/index.md` accordingly. The mirror in `instructions/xwiki-org.md` already names the topic, so it is untouched. Co-Authored-By: Claude Opus 5 (1M context) <noreply(a)anthropic.com> To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-dev-llm/settings/notifications

1 0

[xwiki-contrib/application-releasenotes] f4253b: RN-105: A change with no title is displayed with a...
by XWiki Notifications 03 Sep '26

03 Sep '26

Branch: refs/heads/master Home: https://github.com/xwiki-contrib/application-releasenotes Commit: f4253b305517800d95a7034542009df6d7fc8441 https://github.com/xwiki-contrib/application-releasenotes/commit/f4253b3055… Author: Vincent Massol <vincent(a)massol.net> Date: 2026-09-03 (Thu, 03 Sep 2026) Changed paths: M application-releasenotes-ui/src/main/resources/ReleaseNotes/Code/Change/ChangeDisplayerFlow.xml M application-releasenotes-ui/src/main/resources/ReleaseNotes/Code/Change/ChangeDisplayerSimple.xml M application-releasenotes-ui/src/test/java/org/xwiki/releasenotes/DisplayChangesMacroPageTest.java Log Message: ----------- RN-105: A change with no title is displayed with an empty heading * Pass the edit link that follows the summary of a title-less change through a variable instead of emitting it from an #if closing the summary line, in the "simple" and "flow" displayers. Velocity drops the newline that ends a line ending with a directive, so the summary no longer closed its paragraph: the screenshots of a change were laid into it, where the gallery displaying them cannot appear at all, being a standalone macro. * Close the summary with a blank line in both displayers, so that the link towards the change page opens a block of its own rather than a paragraph nested inside the one the summary ends with. * Cover the three displayers that show the media of a change with a page test rendering a change that has both screenshots and a description, asserting that nothing fails to render and that no paragraph nests another. Co-Authored-By: Claude Opus 5 (1M context) <noreply(a)anthropic.com> To unsubscribe from these emails, change your notification settings at https://github.com/xwiki-contrib/application-releasenotes/settings/notifica…

1 0

[[email protected]][Issue] Updates for XWIKI-24799: Netflux server-side idle timeout is hardcoded at 65s and kills healthy realtime sessions in throttled background tabs (server-side counterpart of XWIKI-23928)
by XWiki Notifications 03 Sep '26

03 Sep '26

1 0

[[email protected]][Issue] Updates for XWIKI-23928: WebSocket disconnects in background tabs due to Chrome's "Intensive Wake Up Throttling"
by XWiki Notifications 03 Sep '26

03 Sep '26

1 0

[[email protected]][Issue] Updates for RN-107: The flow displayer misaligns a change's media and displays none when the change has no screenshot
by XWiki Notifications 03 Sep '26

03 Sep '26

1 0

[[email protected]][Issue] Updates for RN-105: A change with no title is displayed with an empty heading
by XWiki Notifications 03 Sep '26

03 Sep '26

1 0

[[email protected]][Issue] Updates for XWIKI-24798: LiveData's state is not persisted in the URL when the macro call enforces a filter
by XWiki Notifications 03 Sep '26

03 Sep '26

1 0