Wikipedia talk:XFDcloser

WT:XFDC

Archives: Index 1, 2, 3, 4, 5, 6

This page has archives. Sections older than 180 days may be automatically archived by when more than 10 sections are present.

XFDCloser not showing up in Vector 2010

Resolved

Tracked in github.com
Issue #63

For some reason, the regular XFDcloser options are not showing up on AFD discussions. I've uninstalled all of the programs and unselected the gadget. Then I selected the gadget again in the Preferences again but still, no options appear that would allow me to close a discussion. What's up here? Liz ^{Read! Talk!} 23:21, 6 June 2024 (UTC)[reply]

This is likely a WP:THURSDAY issue. They done broke something big in this one because it's not the only one I've seen today. Primefac (talk) 00:34, 7 June 2024 (UTC)[reply]

Also noting that this has been (properly) reported at WP:VPT. Primefac (talk) 00:35, 7 June 2024 (UTC)[reply]

Yes, I went to VPT when I realized that I was unlikely to get a response here. And yet, I did! Liz ^{Read! Talk!} 03:53, 7 June 2024 (UTC)[reply]

I'm able to reproduce. Will load up the dev version and step debug it after dinner. P.S. It's broken in Vector and not Timeless, so maybe they implemented mw:Heading HTML changes on modern skins (vector, vector-2022, minerva) today. WP:THURSDAY. –Novem Linguae (talk) 04:25, 7 June 2024 (UTC)[reply]

Should be

Fixed. –Novem Linguae (talk) 06:51, 7 June 2024 (UTC)[reply]

Looks like, thanks! Primefac (talk) 10:21, 7 June 2024 (UTC)[reply]

Links not showing up in XFDcloser beta version

I am on Vector Legacy 2010 (always have been) and the problem persists. Jay 💬 13:00, 7 June 2024 (UTC)[reply]

Link to example page? Ill try loading your common.js and see if something is conflicting. –Novem Linguae (talk) 13:30, 7 June 2024 (UTC)[reply]

I was referring to RfD. Sorry for not mentioning. I have switched to Vector 2022 temporarily until Vector 2010 is fixed. Jay 💬 05:34, 8 June 2024 (UTC)[reply]

@Jay. I am unable to reproduce at Wikipedia:Redirects for discussion/Log/2024 June 1#2023-24 Major Clubs Limited Over Tournament. I see green close, quickClose, and relist links. Can you please confirm you don't see them? Can you also please post a screenshot? Do you have any WP:CONSOLEERRORs? –Novem Linguae (talk) 10:35, 11 June 2024 (UTC)[reply]

I don't see the green close, quickClose and relist links. When I change my skin from Vector 2010 to 2022, and refresh the RfD page, I see them. When I switch the preference back to 2010, the links are no longer seen. How do I post a screenshot? I was on Edge, but tried on Chrome as well. I see console errors like

2024_June_1:547  This page is using the deprecated ResourceLoader module "codex-search-styles".
[1.43] Use a CodexModule with codexComponents to set your specific components used: https://www.mediawiki.org/wiki/Codex#Using_a_limited_subset_of_components
(anonymous) @ 2024_June_1:547
startup.js:1307  This page is using the deprecated ResourceLoader module "jquery.ui".
Please use Codex instead.
execute @ startup.js:1307
startup.js:1307  This page is using the deprecated ResourceLoader module "mediawiki.ui".
[1.41] Please use Codex. See migration guidelines: https://www.mediawiki.org/wiki/Codex/Migrating_from_MediaWiki_UI
execute @ startup.js:1307
index.php?title=User:PrimeHunter/Source_links.js&action=raw&ctype=text/javascript:36
10Third-party cookie will be blocked. Learn more in the Issues tab.

— Preceding unsigned comment added by Jay (talk • contribs)

Thanks for that. Deprecation notices aren't anything to worry about. We're looking for things like "error" and "uncaught". Here's a graphic with more details about what to look for in the console.

To take a screenshot, you press your "Prt Scn" key, open a graphics program such as MS Paint, paste it in, save it, then upload it somewhere. Third party sites like imgur.com can be good for this if you're OK with not using FOSS. If you want to upload it to Commons for FOSS reasons, then you'd want to use c:Special:UploadWizard, although there are many more restrictions due to copyright. For example, you're supposed to crop out your operating system unless it's Linux, and you're only supposed to screenshot open source browsers such as Firefox, rather than proprietary software such as Chrome or Edge.

Two useful screenshots would be 1) the RFD page (so I can verify your skin) and 2) the console (so I can look at the error messages). –Novem Linguae (talk) 11:53, 11 June 2024 (UTC)[reply]

Actually, don't worry about the screenshots. I was able to reproduce this just now. Let me dig into it and I'll get back to ya. –Novem Linguae (talk) 11:58, 11 June 2024 (UTC)[reply]

[edit conflict] No, there are no errors. I know to take screenshots, uploading them was the question. Definitely do not want to upload to Commons where it will be permanent. Same for imgur I guess. Is there a site where images are kept for a day or so and purged? That will be perfect for screenshots. Jay 💬 12:03, 11 June 2024 (UTC)[reply]

Sent you the requested screenshots. Jay 💬 18:40, 11 June 2024 (UTC)[reply]

@Jay, Hey man im josh, and The Herald:. I deployed a fix related to the beta version of XFDcloser. Can you try again and let me know if things are fixed? –Novem Linguae (talk) 00:50, 13 June 2024 (UTC)[reply]

@Novem Linguae: It's back for me, at least with desktop mode from Chrome browser on my phone. Hey man im josh (talk) 00:57, 13 June 2024 (UTC)[reply]

Yes, awesome, you are the GOAT! Jay 💬 05:30, 13 June 2024 (UTC)[reply]

Amazing. Works perfect. I just love Monobook and didn't wanna switch. Thank you and happy editing :) — The Herald (Benison) (talk) 13:02, 13 June 2024 (UTC)[reply]

July

I am using Vector 2022 and the XFDcloser options are not appearing for me. ✗plicit 23:40, 18 July 2024 (UTC)[reply]

mw:Heading HTML changes#Wikimedia wikis. I need to release another patch :( –Novem Linguae (talk) 23:43, 18 July 2024 (UTC)[reply]

Fixed. Hotfix released. Should take effect within 15 minutes as caches clear. –Novem Linguae (talk) 00:21, 19 July 2024 (UTC)[reply]

That was quick. Thanks! ✗plicit 02:34, 19 July 2024 (UTC)[reply]

Request to change script to use certain template

Tracked in github.com
Issue #90

I was wondering if you could make a slight modification to this script so that it uses Template:XfD relist over the redirect Template:Relist. I want to make the redirect a dab page, so any help with that script would be greatly appreciated. Interstellarity (talk) 20:01, 12 August 2024 (UTC)[reply]

@Interstellarity: For what it's worth, I'm all about having this gadget use the target instead of the redirect, but converting Template:Relist into a disambiguation page is controversial: Such a major change to the way things have been done for over a decade probably needs discussion at WP:RFD. Steel1943 (talk) 16:24, 22 August 2024 (UTC)[reply]

@Steel1943: Thanks. I might consider listing the redirect at RFD at some point, but I don't see a need right now to do it. Interstellarity (talk) 00:59, 23 August 2024 (UTC)[reply]

Relist date calculation bug

Tracked in github.com
Issue #91

Hello, whomever watches this talk page,

I'm using XFDCloser and, for some reason, when I relist a discussion from the AFD daily log for August 6th, it gets posted on Wikipedia:Articles for deletion/Log/2024 August 12 instead of Wikipedia:Articles for deletion/Log/2024 August 13 even though it is almost 04:00 UTC, well into August 13th. This isn't the first time this has happened but it usually gets resolved after an hour or two into the new day. Any assistance or suggestions would be welcome. Liz ^{Read! Talk!} 03:54, 13 August 2024 (UTC)[reply]

This is likely a user-side issue rather than a tool issue; I've had that before when not in UTC itself. Primefac (talk) 11:51, 13 August 2024 (UTC)[reply]

Can you link an example please? Also, what is your time zone? If you're comfortable giving it out. –Novem Linguae (talk) 12:48, 13 August 2024 (UTC)[reply]

I can give one myself, Special:Diff/1235376090 and Special:Diff/1235376112. I was traveling at the time; it's happened to me before and seems to occur when my local time does not match my computer time. Primefac (talk) 13:02, 13 August 2024 (UTC)[reply]

TFD/FFD relist wikicode

Hi, I don't use XFDcloser so sorry if this makes no sense. Recently I was confused by a line looking like this:

Relisted on 01 Jan 1901.

but with all the other links around I never thought that the way to go to the relisting was to click on the date. A wikilink text should say what the link will go to, but this one does not. So I propose that it instead should look like one of these:

Relisted on 01 Jan 1901.

Note that these link to the same place but now it says that the relisting is there whereas it didn't before. Perhaps this comment applies to other things too; I don't know. Thanks for considering. Zero^talk 13:00, 25 August 2024 (UTC)[reply]

Got a diff? There's a lot of different xfd log pages and I want to make sure we're talking about the same one. –Novem Linguae (talk) 13:53, 25 August 2024 (UTC)[reply]

I believe it is content such as Wikipedia:Templates for discussion/Log/2024 July 30 § Template:Move topicon. Primefac (talk) 14:24, 25 August 2024 (UTC)[reply]

Yes, that's it. In my case it was an image, but same idea. Zero^talk 14:50, 25 August 2024 (UTC)[reply]

OK, I'm glad I asked. This appears to be TFD only. For example RFD has a different look and different templates for its relists. I found the TFD manual relist instructions, which are at Wikipedia:Templates for discussion/Closing instructions#Relisting. Can the change you're asking for be made in one of those templates, or do we think it's hard-coded into XFDcloser? Here's some other templates that may be involved in relisting TFDs: https://github.com/wikimedia-gadgets/xfdcloser/blob/077d0b2f4f8d03cc9d20526f9cc7bbde3050fe26/xfdcloser-src/Venue.js#L170-L177. –Novem Linguae (talk) 15:34, 25 August 2024 (UTC)[reply]

{{Tfd top}} doesn't format anything, notice that in #Closing the discussion the full close is input as a parameter. I suspect XFDC (and probably Doug's old extension which I still use occasionally) just used that logic as well. I am still thinking about whether I think this is a helpful change vs changing a well-used and long-standing format/convention. Primefac (talk) 16:05, 25 August 2024 (UTC)[reply]

We could try using clearer wording. For example, changing the current wording of

The result of the discussion was relisted on 2024 August 6

to

The result of the discussion was relisted (please see the 2024 August 6 TFD discussion page)

Bummer that it's not controlled by a template. That makes this harder to change. Perhaps too hard to be worth it. –Novem Linguae (talk) 16:15, 25 August 2024 (UTC)[reply]

It's not only TFD. Here is an FFD example. Zero^talk 00:55, 26 August 2024 (UTC)[reply]

Add draftify result?

Tracked in github.com
Issue #68

Can I firstly say, thank you so much Novem Linguae for all your work with patching and bug investigating over the past couple of months - you are an unsung hero!

This is a very greedy wishlist request but I was wondering if there was capacity at some point in the future to add "draftify" as one of the results for AfD? It seems to be a reasonably common outcome nowadays and, while it is eminently achievable by using "custom" and then actioning all the page moves etc., would be amazing for it to be all bundled up. Fully understand if not possible though, or not a priority given everything else happening.

Cheers, Daniel (talk) 13:05, 28 August 2024 (UTC)[reply]

Looks like Vanamonde93 already requested this back in 2022. Ticket. I'll slap a high priority tag on it since it is now requested by multiple people. (This just means that if a volunteer dev ever sits down to work on tickets, hopefully they consider prioritizing it. There's no active development at the moment.) By the way, can you go into a bit more detail about the "extra steps" for drafts? Is the only extra step moving the page to the draft namespace, or are there other steps? Thanks. –Novem Linguae (talk) 13:19, 28 August 2024 (UTC)[reply]

It's late here but to my memory, click 'custom' > type "draftify" > close > go to article > move article (and tick 'move talk page' and 'do not leave redirect') > comment out categories on draft page (could be automated?). The bot adds the 'draft from mainspace' template afterwards. Might be something else? Daniel (talk) 13:25, 28 August 2024 (UTC)[reply]

I feel like a slight tweak of this would actually make it more useful across more circumstances. For example, at TFD there are (not super-often) "userfications" made to templates, where the template is moved to a userspace, similar to a draftification at AFD. It might be worth having a generic "move" option in the closer options, where the closer can choose the new name of the page (e.g. "Example -> Draft:Example" or "Template:Example -> User:Joe/Template:Example") which could do the move-without-redirect. I do recognise that moving pages is a bit more involved than just editing or deleting pages, so if that sort of expanded functionality is too much, then I guess I'll just have to live with it! Primefac (talk) 13:34, 28 August 2024 (UTC)[reply]

Seems like there could be 3 additional modes to add here: AFD draftify, AFD userfy, and TFD userfy. Any others? I'm not sure a move feature would be as useful for things like CFD, RFD, and FFD. Draftify has enough unique stuff going on (turning off categories, adding Moved Draft template) in it that it may make sense to keep it separate. There's also some positives to pre-programming the correct terminology in. For example "draftify" would probably be better to write in an AFD close than "move to Draft:X". –Novem Linguae (talk) 13:57, 28 August 2024 (UTC)[reply]

Just noting that I came here ot ask the same question. This is an amazingly helpful tool, this functionality would just make it that much better. Just Step Sideways ^{from this world ..... today} 01:56, 24 November 2024 (UTC)[reply]

Allow non-admins to close CFDs

Tracked in github.com
Issue #92

Hi! I have an easy (I think?) request: Like at WP:TFD, non-admins are permitted to close discussions at WP:CFD as delete (see WP:NACD for the official guideline saying deletion NACs at CFD are okay). Would it be possible to enable this option for non-admins at CFD, like how it is enabled at TFD? Thanks, House Blaster (talk • he/they) 23:18, 20 September 2024 (UTC)[reply]

@HouseBlaster. Are there any CFD workflows that would change by not having the delete button? For example, for non-admins, maybe instead of trying to delete the page, the gadget would instead need to add the page to a queue / holding cell?

If the admin vs non-admin CFD workflows are the same, this is easy. If the workflows are different, this is hard. –Novem Linguae (talk) 23:12, 23 September 2024 (UTC)[reply]

@Novem Linguae: the workflows are identical at this stage in the process: XFDC only closes the discussion, and nothing else – not even deleting the page. Non-admins list their closures at WT:CFDW, but that is facilitated by a separate script (User:Qwerfjkl/scripts/CFDlister). Admins have to list the discussions directly at WP:CFDW, but that is not handled by XFDC. House Blaster (talk • he/they) 23:34, 23 September 2024 (UTC)[reply]

Oh, besides the fact that NACs should get tagged with {{subst:nacd}}. Otherwise identical. House Blaster (talk • he/they) 23:50, 23 September 2024 (UTC)[reply]

Nomination for merger of Template:Rfd-NPF

Template:Rfd-NPF has been nominated for merging with Template:Redirect for discussion. Watchers of this page are invited to comment on the discussion at the template's entry on the Templates for discussion page. Thank you. Steel1943 (talk) 22:16, 22 September 2024 (UTC)[reply]

I don't see this template in XFDcloser's code. Probably no action needed here. –Novem Linguae (talk) 23:23, 23 September 2024 (UTC)[reply]

@Novem Linguae: You are correct, it is probably not; however, this template does appear on redirects tagged by PageTriage, and as hinted above in the top section of this talk page, XFDcloser is not able to remove these tags from redirects after their respective RFD discussions have been closed. Steel1943 (talk) 17:31, 24 September 2024 (UTC)[reply]

XFDcloser creating erroneous edit summaries and linking to Undefined after AfD/PROD closures

Tracked in github.com
Issue #93

Long story short, see this diff and the clearly erroneous link to Undefined. This is one diff of many I found with the same issue, but I think only one needs to illustrate the problem. Steel1943 (talk) 16:16, 23 September 2024 (UTC)[reply]

@Steel1943. Have you noticed any pattern to this (for example links with spaces, links in a certain namespace, etc.), or does it always happen when XFDcloser removes any wikilink? –Novem Linguae (talk) 23:08, 23 September 2024 (UTC)[reply]

@Novem Linguae: Looking through some more recent edit summaries that include the link to undefined, it seems that this link is only caused by delinking pages that have been deleted through the PROD process, not AfD (contrary to what I originally assumed), and happens in title with or without spaces (from what I saw). The only way I was able to figure this out is because Explicit does a good amount of deletions, so I was able to see this pattern. (Explicit, thank you for all that you do; sorry this tool has not been working correctly and makes your PROD article delink edit summaries look wrong.) Steel1943 (talk) 17:36, 24 September 2024 (UTC)[reply]

@Primefac: To answer your since-removed comment since you make a good point that I was not aware of myself until you made the comment, it seems that the deletion itself is performed by Twinkle (see Animal Behavior Society), but XFDcloser does the delinking of the page deleted via PROD. Does that mean that Twinkle and XFDcloser interface with each other when both are enabled? (Not sure, and I'm not sure who would know.) Steel1943 (talk) 17:24, 25 September 2024 (UTC)[reply]

They are probably independent of each other. An undefined in XFDcloser's edit summary is almost surely a bug in XFDcloser, not Twinkle. –Novem Linguae (talk) 20:50, 25 September 2024 (UTC)[reply]

@Novem Linguae: I definitely agree and understand that it is XFDcloser causing the error with the delinking edit summary problems. However, the timestamps for the PROD deletion of Animal Behavior Society (Twinkle) and the delinking of a link to it in another article (the diff in my initial statement [XFDcloser]) are identical. This leads me to believe one of the following: 1) Twinkle has an option built into it to perform delinkings with XFDcloser after a PROD, thus meaning XFDcloser is not sure what to link as a result, or 2) the issue may be caused by user error, possibly by running Twinkle and XFDcloser almost simultaneously. Steel1943 (talk) 21:04, 25 September 2024 (UTC)[reply]

I see. I've added https://github.com/wikimedia-gadgets/xfdcloser/issues/93#issuecomment-2375372798 to remind myself or whoever to investigate this more when the ticket is being further researched. –Novem Linguae (talk) 22:24, 25 September 2024 (UTC)[reply]

I've cross-posted to WT:TW to see if it's an issue on their end. Primefac (talk) 12:04, 26 September 2024 (UTC)[reply]

The bug is not related to Twinkle. PROD deletions are only supported in Twinkle, and although Twinkle has its own Unlink tool, XFDC's unlinking is more feature-rich, so many users tend to prefer that – you can see the option on any non-existing page under "Tools" (vector-2022) or in the "More" dropdown (vector-2010). – SD0001 (talk) 18:12, 26 September 2024 (UTC)[reply]

the issue may be caused ... possibly by running Twinkle and XFDcloser almost simultaneously I don't think so, it's also been known to occur when you unlink 3 months after the page was deleted. – SD0001 (talk) 18:16, 26 September 2024 (UTC)[reply]

But... you can't even use XFDC if you're not on an XfD page... Primefac (talk) 18:20, 26 September 2024 (UTC)[reply]

You can. – SD0001 (talk) 18:33, 26 September 2024 (UTC)[reply]

Based on all that has been stated so far, seems both of my assumptions are incorrect and the examples that I provided from Explicit show that they are a fast clicker and that the two gadgets do not technically interrupt each other, meaning this probably has nothing to do with Twinkle. But, it seems there may be a new theory here: Do links to undefined in edit summaries only occur via the "XFDC Unlink" option when the respective page is deleted before running "XFDC Unlink"? Steel1943 (talk) 18:46, 26 September 2024 (UTC)[reply]

I tried to test this by adding a wikilink to a non-existent page to my sandbox and to a mainspace redirect. I couldn't get the XFDC Unlink tool to remove them. I don't really want to add a test link to a live article, so might be hard to test this. Might need to install the gadget on testwiki and mess around with it there to do it properly.

Anyway, I've updated the ticket with the latest hypothesis: https://github.com/wikimedia-gadgets/xfdcloser/issues/93

Also, I wonder why we don't have a mainspace sandbox. Would make certain kind of tests much easier. Maybe we could hard-code it into MediaWiki to always noindex it. –Novem Linguae (talk) 20:47, 26 September 2024 (UTC)[reply]

XFDcloser adds |2=[Article Name] to RFD templates

What do these changes do? 1, 2. They don't update the RfD link or anything. Hyphenation Expert (talk) 06:16, 3 November 2024 (UTC)[reply]

It ensures the link in the RFD/core template will go to the correct section of the initial nomination date subpage, especially with nominations with multiple redirects. Steel1943 (talk) 18:31, 5 November 2024 (UTC)[reply]

Maybe it used to do that, but no longer? Using Scottish Nosepickers as an example... Both before and after the relist change (2=Scottish Nose-pickers), the RfD link still just uses the page title as anchor (#Scottish_Nosepickers). And the anchor already works regardless because every nom in a multi-nom has its own "span-id" element. Hyphenation Expert (talk) 23:49, 5 November 2024 (UTC)[reply]

Rfd-NPP not recognized

Tracked in Phabricator
Task T375440

May be unrelated, but much of the time closing as Keep at RfD does not do anything to the redirect page. I have to manually remove the deletion notice and tags. I'm on Vector Legacy (2010). Jay 💬 07:05, 3 November 2024 (UTC)[reply]

@Jay: It's probably unrelated: XFDcloser doesn't recognize {{Rfd-NPF}} (specifically {{Rfd-NPF/core}}), the RFD tag placed by PageTriage. It's been a huge headache for a while. Steel1943 (talk) 18:29, 5 November 2024 (UTC)[reply]

Relisted on wrong day on WP:RFD

Tracked in github.com
Issue #91

See these edits: [1] [2]; these edits occurred on 5 November 2024, but XFDcloser relisted the discussion on the 4 November 2024 (1 day earlier) page. Steel1943 (talk) 18:26, 5 November 2024 (UTC)[reply]

Steel1943, known bug: https://github.com/wikimedia-gadgets/xfdcloser/issues/91 — Qwerfjkl talk 19:16, 5 November 2024 (UTC)[reply]

Indeed, I seem to recall it has to do with the user time rather than UTC. Primefac (talk) 20:12, 5 November 2024 (UTC)[reply]

Yep, annoying stuff like that is why I leave my time preference on Wikipedia as UTC. Prevents a whole lotta garbagio, and is probably the easiest workaround. Steel1943 (talk) 20:39, 5 November 2024 (UTC)[reply]

@Significa liberdade: FYI. Steel1943 (talk) 21:21, 5 November 2024 (UTC)[reply]

Would this still be the case if I made the edits on November 5 at 10:20 AM my time? I can understand this occurring if it were November 4 my time but November 5 UTC, but it seems odd if both are on the same day. Significa liberdade (she/her) (talk) 21:24, 5 November 2024 (UTC)[reply]

Can't say for certain. This gadget has been wonky for a while, and it hasn't been maintained for a few years. Only thing most have been doing is reporting bugs and figuring out the workarounds and using those so the tool will work for them. For me, I have left my global time zone set as UTC, even though it's not my actual time zone, and I have yet to have any odd issue happen with tools or gadgets based on timestamps. Steel1943 (talk) 22:34, 5 November 2024 (UTC)[reply]

Figure I'd add to this: Since this tool is widely used, though not recently maintained at all, in 2022, an editor made some REALLY great updates to {{Rfd2}}, but ... they had to be reverted due to how this tool works and since there was no one available to update this tool to work for {{Rfd2}}'s new functionality at the time. 😫 Steel1943 (talk) 22:40, 5 November 2024 (UTC)[reply]

Close log

Tracked in github.com
Issue #94

I think it would be very nice to have the tool automatically keep a close log, like twinkle does for CSD and AfD noms.

Kingsmasher678 (talk) 19:42, 4 December 2024 (UTC)[reply]

Delinking/delisting Bug?

Tracked in github.com
Issue #95

Is this an existing or known bug, shouldn't the script be delinking instead of removing entirely? — Paper9oll (🔔 • 📝) 12:12, 21 December 2024 (UTC)[reply]

The edit summary says "removing links / list items". The "removing list items" part makes it seem like it might be intentionally programmed this way. Interesting. If so, I think just always de-linking might be a bit safer. –Novem Linguae (talk) 13:21, 21 December 2024 (UTC)[reply]

Ya, I think it would be safer to change it do delinking as this wasn't caught until a day later by a new editor. — Paper9oll (🔔 • 📝) 13:26, 21 December 2024 (UTC)[reply]

Header changed to a more descriptive one

Per Wikipedia:XFDcloser#Unlinking_backlinks this is an issue with the closer not pressing the right buttons. In other words, it is not a bug. Primefac (talk) 13:35, 23 December 2024 (UTC)[reply]

Thanks for that link. I didn't realize that each list removal prompted the user to manually approve it. It should be safe to keep this feature.

Closing without action –Novem Linguae (talk) 17:25, 23 December 2024 (UTC)[reply]

Noted, thanks! — Paper9oll (🔔 • 📝) 18:52, 23 December 2024 (UTC)[reply]

Unable to type in Multiple results

Tracked in github.com
Issue #96

I started seeing the problem on Sep 9 or 10 (see WT:Redirects for discussion#XFDcloser is broken), but it may have been there from earlier. Typing into the Result Summary or Rationale fields of the XFDcloser is not possible. It treats characters as keyboard shortcuts and does other stuff. Apparently it happens for Multiple results only. Jay 💬 06:54, 25 September 2022 (UTC)[reply]

Also typing in something in the RCAT page of the wizard messes up the earlier result selections. I typed R and all my results went back to Retarget

. Jay 💬 06:56, 30 September 2022 (UTC)[reply]

@Evad37: Can a bug be filed for this, or maybe revert the September 9-10 change that caused this regression? Jay 💬 11:09, 20 November 2022 (UTC)[reply]

This happens on Firefox which I use. This doesn't happen with Chrome. But today, I see that the Multiple results option is fully broken. The "Next" button is not getting enabled. Jay 💬 08:36, 4 February 2023 (UTC)[reply]

So any time I have to close a RfD with multiple results, I log out of Firefox, log in to Chrome, and do the close.Whatever change was made to this tool in Sep 2022 should be reverted. Jay 💬 13:48, 26 March 2023 (UTC)[reply]

I had this same problem – I had to copy/paste my rationale, etc. from a separate page. When I typed "S", everything went to "Soft redirect". Can someone please fix this? It was quite annoying Edward-Woodrow :) _[talk] 19:58, 14 August 2023 (UTC)[reply]

Ran into this bug again today on Firefox after seemingly not having seen it for a while. _signed,Rosguill ^talk 17:25, 8 October 2023 (UTC)[reply]

Today I closed an RfD where one of the entries was Delete and the other was Retarget, but the delete entry was not actually deleted but retargeted to "null". Jay 💬 14:28, 27 December 2024 (UTC)[reply]

@Jay. Do you think this is still a Firefox-only bug? Were you using Firefox for this particular close? –Novem Linguae (talk) 20:33, 27 December 2024 (UTC)[reply]