Stop having accounts renamed multiple times...

They are not my accounts though so I have no influence on how other people rename their accounts on all wikis.

Special:DoubleRedirects is full of such renames as evidently people do rename two or more times fairly often.

The user rename issue is a red herring. The issue here is that after a page move, CSS and JS redirects behave in a very funky way. I changed the summary from "Handling of .js and .css pages post rename" to "Handling of .js and .css pages post page move".

A few parts to this. Behavior is user moves a JS/CSS page from one title to another using MediaWiki page move form. This leaves behind a redirect (by default).

Redirect's current behavior is broken by the page's syntax highlighting, which assumes that everything in the text area of a page ending in .css or .js is CSS or JS. (This bug might be a duplicate.)

Problems with not redirecting:

• it's annoying as hell that the redirects don't work as you'd expect them to

Problems with redirecting:

• redirects can't easily be edited
  • still usually need an admin account to do any edits due to the redirect page titles still ending in .css/.js and getting special protection for it
    • users editing their own personal .css/.js pages shouldn't hit this issue
  • bots trying to fix double redirects hit walls
• sets up a false expectation about following these redirects programmatically, maybe?
  • not sure what behavior is here nowadays with ResourceLoader

I run my bot on practically every wiki and these need to be dealt with manually or else they pile-up eventually rendering Special:DoubleRedirect's useless.

How about... instead of converting .css and .js pages into "#redirect[[foo]]", they are turned into "importScriptURI('url to foo');"

Code would continue operating and not flood double redirects. This can be done when the account is being renamed.

See also:

• Bug 33973
• Bug 30074
• bug 31827

(In reply to comment #0)

1. Ignore .css and .js pages while populating Special:DoubleRedirects

No.

3. Allow bots to edit .css and .js pages if these pages are redirects or allow

bots to edit .css and .js pages like admins.

Never ever. Major security leak that would be.

2. Do not create a redirect after moving .css and .js pages

Sounds good, that's a task for the Renameuser extension. Rephrased this bug for that.

2. Do not create a redirect after moving .css and .js pages

Sounds good, that's a task for the Renameuser extension. Rephrased this bug for
that.

Why not to fix T35973 instead?

(In reply to comment #7)

2. Do not create a redirect after moving .css and .js pages

Sounds good, that's a task for the Renameuser extension. Rephrased this bug for
that.

Why not to fix bug 33973 instead?

That is a separate bug, which may be an invalid bug, even.