User talk:Eejit43

redirect-helper: Dark mode support

Thanks for your work on redirect-helper! You might know this already, but dark mode support on it is subpar. Everything except the text boxes are the same as light mode. If this could be improved it would be greatly appreciated. Thanks so much, Axolitl (talk | contribs) 03:32, 12 July 2026 (UTC)

@Axolitl thanks for the reminder on this issue, it's finally given me the push I needed to get it done! Dark mode is now fully supported across all my user scripts, including redirect-helper. It uses Codex design tokens so it should match the colors across the rest of the site, but let me know if you run into anything that looks off. ~ Eejit43 (talk) 03:19, 13 July 2026 (UTC)

afcrc-helper

Hello, sorry for disturbing you as you are currently sleeping, but I'm dropping this msg before I head for my exams, but the script (afcrc-helper) keeps showing reviewed request as unreviewed, don't know if this a bug or what. In solidarity, Destinyokhiria _{(talk / cont)} 06:31, 13 July 2026 (UTC)

Sorry about that, looks like I forgot to rebuild after undoing a change I'd made for debugging dark mode. Fixed now! ~ Eejit43 (talk) 13:21, 13 July 2026 (UTC)

redirect-helper

redirect-helper often tells me that an anchor doesn't exist while in reality it does exist. I'm used to clicking "auto-fix" when it tells me that the redirect should be tagged with "{{r to section}}" or {{r to anchor}}, but when it doesn't recognise the anchor i instinctively click "Auto-fix" and it just deletes the name of the section from the target field! Argh!

I think the whole error>auto-fix flow could be vastly improved, but I think the script should at least check more thoroughly if that anchor really doesn't exist on that page. I notice this often happens when the anchor is inside {{va}} on the target page. FaviFake (talk) 09:53, 16 July 2026 (UTC)

Very frustrating! Unfortunately parsing anchors like that is quite difficult. Currently I parse the page source to pull out anything that would manually add element IDs (making anchors), but it's obviously very complex to find all those cases.

I can try to do a different method and use the parsed HTML output and try to find anchors that way (which I probably should have done all along!). Do you have a page on hand where the the anchor detection didn't work? Regardless, I think I'll work on using this method instead. It may have false positives if some templates emit things with IDs that aren't intended to be linked to, but there's nothing that can be done about that really. I could also add some way to display all anchors upon request, but probably wouldn't do this automatically for performance reasons. ~ Eejit43 (talk) 22:03, 16 July 2026 (UTC)

Very frustrating!
Yes!
Do you have a page on hand where the the anchor detection didn't work?
Wikipedia:What Wikipedia is not is an amazing testing ground. For whatever reason, there are literally hundreds of anchors in all shapes and sizes. For example, if you try to change the shortcut WP:NOT to Wikipedia:What Wikipedia is not#PAPER, which is a working anchor, the script will say it doesn't exist and prompt you to remove it. I've tested a few {{va}}s but those seem to work; PAPER, however, is inside a {{sh}} template! FaviFake (talk) 22:46, 16 July 2026 (UTC)

For the record the anchor is added through <span class="anchor" id="PAPER"></span><span class="anchor" id="NOTPAPER"></span>Wikipedia is not a paper encyclopedia, and somehow it looks like I set up parsing incorrectly for that, where it always fails as it mistakenly includes the leading quotation mark in the valid title list. So, anchors like that don't work in most cases...

Welp, I'll definitely go for this other option, too many edge cases with this method. Should be simpler too! ~ Eejit43 (talk) 23:28, 16 July 2026 (UTC)

Oh, my mistake!

So, anchors like that don't work in most cases
Yeah that's not great, as WP:ANCHORSUBST prescribes that exact method for section anchors. FaviFake (talk) 12:15, 17 July 2026 (UTC)

Another example is WP:NOTWHATFIRSTCOMESTOMINDWP:NOTWHATFIRSTCOMESTOMIND. the script doesn't recognise that Wikipedia:Disambiguation#Not .22what first comes to mind.22 is a valid anchor. FaviFake (talk) 16:28, 19 July 2026 (UTC)

@FaviFake I've now finished my work on this, and redirect-helper now shows anchors in the title dropdown, and validation should now reflect all anchors in a text (though I've excluded cite anchors as those won't be used). Please give it a test and let me know if you run into any issues!

Regarding WP:NOTWHATFIRSTCOMESTOMIND, that should really use an actual quote character instead of the encoded ".22". It correctly recognizes this now though. ~ Eejit43 (talk) 21:32, 19 July 2026 (UTC)

though I've excluded cite anchors as those won't be used
Actually, these are used sometimes, for example this one was used until last year: Special:Permalink/1166431134. However, you're right to exclude them. The probability that someone will create such a redirect is so low that it's not worth searching for it or suggesting it.

Thanks so much for your work! I have no idea what language redirect-helper is written, or how much free time you have, or if these scripts are even similar in any way, but would you be interested in also helping updating the XFDcloser script? There are a few updates needed after the PAM-AFD merge in case you're interested or able to write code for it. FaviFake (talk) 21:50, 19 July 2026 (UTC)

How interesting! Yeah, definitely not something that is usually done though, if someone really wants it they'll have to live with being warned!

Happy to! This was definitely needed, despite it taking a while I'm very happy to have done it :)

redirect-helper is written in TypeScript for the record, though this is a simple conversion to JavaScript as all user scripts/gadgets use. Unfortunately I don't really have time at the moment to work on XFDcloser, but I hope someone with some more free time can come along and work on it! ~ Eejit43 (talk) 23:13, 19 July 2026 (UTC)

Hey, I thought you'd be interested in a couple more annoyances I often encounter when using the script, both of which have to do with submitting the edit. Firstly, the three edit summary suggestions "Resolve double redirect - Resolve self redirect - Remove incorrect rcats" are pretty useless in my opinion. For double redirects and self redirects, the script could check that itself without the user having to specify it, and for the last one the script could just change the default edit summary to specify which rcats were removed.

Other than not being very useful, they are annoying simply because they hide the Submit button, even when I've already started typing my custom edit summary. Normally, to avoid having to use the mouse, I would click Enter on my keyboard, but that doesn't work on your script, both in the "Target" field and in the edit summary field :( FaviFake (talk) 14:22, 26 July 2026 (UTC)

Thanks for letting me know! I've removed the summary suggestions as I agree they were wholly unhelpful. I've also made it so pressing "enter" will submit the form from the summary input. I didn't do that for the target field seeing as you use the same buttons to select dropdown options, and that could result in unintended submissions.

As for updates to the default summaries, those could be done but for double redirects it would require an API request when opening the form which is not ideal. Checking for self redirects is trivial but would be rarely used, but it could be done! The reason it doesn't show what rcats were added/removed is because that could easily cause the summary length limit to be exceeded. ~ Eejit43 (talk) 20:37, 26 July 2026 (UTC)

Thanks! This is perfect!

Yeah, honestly I don't really care about any of these, I only use the script to create new redirects and to tell me when I forget to add {{r to section}}. Thanks so much for the Enter thing, it works great! FaviFake (talk) 20:47, 26 July 2026 (UTC)

Installing article-cleaner

I installed article-cleaner at User:Nurg/common.js and did a hard refresh but nothing new appears on my More menu when in edit mode. I deleted everything else in common.js in case there was a conflict, but it still doesn't appear. I tried adding it to User:Nurg/vector.js but still no joy. I am using the latest Chrome, Version 151.0.7922.72. I also tried in Firefox, which I haven't opened for some time, but no go there either. Any suggestions? Thanks. Nurg (talk) 02:37, 3 August 2026 (UTC)

Hello @Nurg! What skin are you using, presumably one of Vector or Vector 2022? And are you using the "2010 wikitext editor" and/or "2017 wikitext editor" as enabled through Special:Preferences? ~ Eejit43 (talk) 03:28, 3 August 2026 (UTC)

Hi, thanks. Vector legacy (2010). Neither the "2010 wikitext editor" nor "2017 wikitext editor" are enabled. Nurg (talk) 07:40, 3 August 2026 (UTC)

Thanks! I found the issue, it was due the CSS that detected the editor being open didn't work for the HTML layout differences in Vector legacy. Should be fixed now, let me know if you have any issues! :) ~ Eejit43 (talk) 17:17, 3 August 2026 (UTC)

It works now. Thanks very much. (Now to see if it will be useful to me.) Nurg (talk) 23:20, 3 August 2026 (UTC)