Change Details

In testing CheckUser using the new x-xss language (as recently announced on Wikitech-l) I found that the following messages cause the display of the alert: * checkuser-log-entry-userips * checkuser-log-entry-ipedits * checkuser-log-entry-ipusers * checkuser-log-entry-ipedits-xff * checkuser-log-entry-ipusers-xff * checkuser-log-entry-useredits * checkuser-log-entry-investigate These are not in the RawHtmlMessages config and as such present this issue. These messages should either be added into this config or properly HTML escaped Example: {F37852730}

In testing CheckUser using the new x-xss language (as recently announced on Wikitech-l) I found that the following messages cause the display of the alert: * checkuser-log-entry-userips * checkuser-log-entry-ipedits * checkuser-log-entry-ipusers * checkuser-log-entry-ipedits-xff * checkuser-log-entry-ipusers-xff * checkuser-log-entry-useredits * checkuser-log-entry-investigate * parentheses Some of the messages that start with `checkuser-log-` contain HTML but are not in the RawHtmlMessages config. The other messages need to be properly escaped. Example: {F37852730}

In testing CheckUser using the new x-xss language (as recently announced on Wikitech-l) I found that the following messages cause the display of the alert: * checkuser-log-entry-userips * checkuser-log-entry-ipedits * checkuser-log-entry-ipusers * checkuser-log-entry-ipedits-xff * checkuser-log-entry-ipusers-xff * checkuser-log-entry-useredits * checkuser-log-entry-investigate * parentheses These are not in the RawHtmlMessagesSome of the messages that start with `checkuser-log-` config and as such present this issuetain HTML but are not in the RawHtmlMessages config. These messages should eiThe other be added into this config ormessages need to be properly HTML escaped. Example: {F37852730}