Hmmmm what about b/c for installations like:
$wgGroupPermissions['sysop']['editusercssjs'] = false; $wgGroupPermissions['foo']['editusercssjs'] = true;
With this commit it breaks the security model.
Perhaps adding back the hook for 'editusercssjs' for compat setting?
Added back 'editusercssjs' regression test on r54194.
Why did you duplicate the existing messages? The new messages are wrong, they imply that both rights work for both CSS and JS. Like I'm guessing
'right-editusercss' => 'Editar las páginas de CSS y JS de otros usuarios', 'right-edituserjs' => 'Editar las páginas de CSS y JS de otros usuarios',
should be more like
'right-editusercss' => 'Editar las páginas de CSS de otros usuarios', 'right-edituserjs' => 'Editar las páginas de JS de otros usuarios',
You should probably just not provide any message, so translators can provide new messages that are correct.
Generally speaking, why don't you just introduce the two new rights and not remove the old right or anything relating to it at all? You need to keep the old right for backward compatibility, so you should keep the old messages too (otherwise ListGroupRights won't work on wikis using the old right), etc. There's no reason for us to not have to support the old right indefinitely.
Restored 'right-editusercssjs', updated message 'right-editusercss' and 'right-edituserjs' for the language used on r54247.