I'm not sure why there's the need to XML-escape the parameters passed to $services.notification.sources.getNotificationParameters($parameters). They are needed to be escaped for the HTML part for sure but for the java part, I don't see the need.
The problem is that it transforms the A&B value for spaces into: A&B which doesn't exist as a space... It would also break for any XML character that needs escaping and that it part of a space name...
Vincent Massol on 04/Dec/25 17:13
I think it's a regression from XWIKI-17052 which modified https://github.com/xwiki/xwiki-platform/commit/f490e0b28e9f9aa755ef26c293f85452ac1a0db9#diff-df6b621d8b03f4a097acf7d488c8f1d0f0a564637113d346c58b0da1983b8476R1117-R1137
I'm not sure why there's the need to XML-escape the parameters passed to {{$services.notification.sources.getNotificationParameters($parameters)}}. They are needed to be escaped for the HTML part for sure but for the java part, I don't see the need.
The problem is that it transforms the {{A&B}} value for {{spaces}} into: {{A&B}} which doesn't exist as a space... It would also break for any XML character that needs escaping and that it part of a space name...
I think it's a regression from XWIKI-17052 which modified https://github.com/xwiki/xwiki-platform/commit/f490e0b28e9f9aa755ef26c293f85452ac1a0db9#diff-df6b621d8b03f4a097acf7d488c8f1d0f0a564637113d346c58b0da1983b8476R1117-R1137
I'm not sure why there's the need to XML-escape the parameters passed to {{$services.notification.sources.getNotificationParameters($parameters)}}. They are needed to be escaped for the HTML part for sure but for the java part, I don't see the need.
The problem is that it transforms the {{A&B}} value for {{spaces}} into: {{A&B}} which doesn't exist as a space... It would also break for any XML character that needs escaping and that it part of a space name...
I think it's a regression from XWIKI-17052 which modified https://github.com/xwiki/xwiki-platform/commit/f490e0b28e9f9aa755ef26c293f85452ac1a0db9#diff-df6b621d8b03f4a097acf7d488c8f1d0f0a564637113d346c58b0da1983b8476R1117-R1137
I'm not sure why there's the need to XML-escape the parameters passed to {{$services.notification.sources.getNotificationParameters($parameters)}}. They are needed to be escaped for the HTML part for sure but for the java part, I don't see the need.
The problem is that it transforms the {{A&B}} value for {{spaces}} into: {{A&B}} which doesn't exist as a space... It would also break for any XML character that needs escaping and that it part of a space name...
I think it's a regression from XWIKI-17052 which modified https://github.com/xwiki/xwiki-platform/commit/f490e0b28e9f9aa755ef26c293f85452ac1a0db9#diff-df6b621d8b03f4a097acf7d488c8f1d0f0a564637113d346c58b0da1983b8476R1117-R1137
I'm not sure why there's the need to XML-escape the parameters passed to {{$services.notification.sources.getNotificationParameters($parameters)}}. They are needed to be escaped for the HTML part for sure but for the java part, I don't see the need.
The problem is that it transforms the {{A&B}} value for {{spaces}} into: {{A&B}} which doesn't exist as a space... It would also break for any XML character that needs escaping and that it part of a space name...
(in short I'm not escaping for the java call but escaping for the HTML display) ?
Vincent Massol on 04/Dec/25 17:18
I think the escaping is causing a lot more issues than this one reported. For example if the user name contains one of ", ', <, >, & there'll be a similar issue.
This message was sent by Atlassian Jira (v9.3.0#930000-sha1:287aeb6)
If image attachments aren't displayed, see this article.