Open main menu

Wikipedia talk:Twinkle

  (Redirected from Wikipedia talk:TW)

e·h·w·Stock post message.svg To-do:

  • Ability to remove maintenance tags from articles using the "tag" module
  • Incorporate one of the many delsort scripts into Twinkle (see WP:DELSORT).
  • Incorporate FurMe into Twinkle.
  • Redesign the tag module with a tabbed interface similar to PageTriage to enhance the user experience while searching for tags
  • Convert, which Twinkle uses for API calls, to use JSON format.


Children's personal infoEdit

The emerging consensus of this discussion at Wikipedia talk:Criteria for speedy deletion is that kids' personal information needs to be oversighted. I'm sure I'm not the only editor who has viewed this material in terms of deletion (U5, A7, G11, G10) in the past. Could we have another option on Twinkle's CSD menu to handle this properly by initiating an oversight request, Special:EmailUser/Oversight, pre-populated along the lines of "Child's personal info at articlename"? Thanks, Cabayi (talk) 10:46, 16 August 2017 (UTC)

Please, please, please! Legacypac (talk) 12:43, 16 August 2017 (UTC)

+1. Lowering the action threshold for this is a big win in terms of ensuring that issues like this get dealt with not by shining a huge spotlight on it (as there are several known cases of nominating for CSD immediately triggering bots to scrape the data and store it on one of numerous SpeedyDeletion wikis) but to make it easier to privately request oversight is a big win. Hasteur (talk) 12:59, 16 August 2017 (UTC)
  • +1 but not limited to child personal data. Twinkle should offer an "email oversight" tab that contains common reasons for oversight or allows entering a custom reason. Regards SoWhy 12:30, 17 August 2017 (UTC)
  • Support offering Twinkle-users a clear and simple way to report stuff which needs to be oversighted. If Oversighters find they are getting sent too many reports for non-oversight-worthy content, then the documentation at Twinkle can be fine-tuned to clarify what does and doesn't need to be reported. PamD 13:07, 17 August 2017 (UTC)
  • There should be language to specify content needs to be removed before oversight is contacted. I'll save everyone my rant about how much content that should be rev del'd or oversight gets through NPP, but the goal should be to hide the content from the general public as quickly as possible, which requires the editor remove it before waiting what can be hours before an oversighter responds. TonyBallioni (talk) 13:28, 17 August 2017 (UTC)
Just blank the personal details on sight, that should remove them from view and hide them from most of the general public and scrappers, who don't know enough to look in the page history, up until the Oversighter fully blocks them. Diego (talk) 14:04, 17 August 2017 (UTC)
Yes. I know: I'm saying Twinkle should make that clear. A lot of people don't know that, though, so education is key here. TonyBallioni (talk) 14:21, 17 August 2017 (UTC)
  • Support, streamlining the processing of content that needs to be removed for BLP reasons is a good thing. Diego (talk) 14:04, 17 August 2017 (UTC)
  • Support per above, but the Oversight team should be made aware of this discussion as this will probably lead to a significant increase in requests and associated decrease in response time, perhaps to unacceptable levels. We may need more oversighters. – Train2104 (t • c) 14:18, 17 August 2017 (UTC)
  • Support. This seems like a very valuable use of the developers' time, for the reasons above. Matt's talk 19:05, 17 August 2017 (UTC)
  • Support - Including Primefac's RevDel option below. - FlightTime (open channel) 01:42, 18 August 2017 (UTC)
  • Support Good idea. Chris Troutman (talk) 03:36, 18 August 2017 (UTC)
  • Support apap04 talk | contributions 22:18, 30 September 2018 (UTC)


Can we add in revdel support as well? I completely understand the importance of a subtle oversight, but revdel is just as important and Twinkle could make such a task much easier. I hate to piggyback on a somewhat-separate topic, but it's been proposed three times now with zero comments from others. Primefac (talk) 01:29, 18 August 2017 (UTC)

  • Yes. Yes. 1000x Yes. For all the reasons I noted above. TonyBallioni (talk) 03:02, 18 August 2017 (UTC)
  • Support Chris Troutman (talk) 03:36, 18 August 2017 (UTC)
  • Strong support for both - the average editor doesn't need to concern himself with the differences between oversight and revdel. I've been at this near 6 years and I'm not sure which is appropriate when, mainly because I don't need to be. Editing school articles primarily as I do, I come across "Tammy Foo is a slut" or "Bill Foo has a huge cock" almost daily. Making a revdel request easier would be a blessing. John from Idegon (talk) 15:36, 18 August 2017 (UTC)
  • Support both - I've had to mosey over to IRC I believe four times in the past two days over these types of things. TimothyJosephWood 10:46, 25 August 2017 (UTC)
  • Support both - I've had to google "copyvio revdel template" far too many times now. Gone shall be those days. 100% support from my side. Jiten Dhandha • talk • contributions • 11:21, 5 September 2017 (UTC)
    • @Timothyjosephwood and Jiten Dhandha: it's not perfect, but until the above gets implemented I've written up User:Primefac/revdel.js. Just add importScript('User:Primefac/revdel.js'); // Linkback: [[User:Primefac/revdel.js]] to your common/vector/etc. Should help with that pesky "what's the code" issue. Let me know if there are any major issues, or other ways I could improve it further. Primefac (talk) 16:21, 8 September 2017 (UTC)
There is absolutely no way I'm going to figure out how to do that without accidentally deleting my entire account. TimothyJosephWood 16:37, 8 September 2017 (UTC)
@Timothyjosephwood: Click this link: Special:Mypage/common.js > (Create the page if not already existent) > Edit page > Copy code exactly the way Primefac mentioned in the comment above > Hit "Save changes" and voila! :P Jiten Dhandha • talk • contributions • 16:51, 8 September 2017 (UTC)
Jiten Dhandha, TJW doesn't have a common.js ;) Primefac (talk) 17:16, 8 September 2017 (UTC)
@Primefac: I havent tested it yet, but I did add the code to my common.js. The prompts look simple and neat so there's no issue there (I see that only 4 ranges are allowed at max, which isnt an issue since I've never come across an article needed more than that). Now to see if it actually works when I come across an article with copyvio issues. Also, thanks for taking the time out to write the script! Jiten Dhandha • talk • contributions • 16:43, 8 September 2017 (UTC)

Implementation detailsEdit

  Doing... I'll take a shot towards implementing this - a revdel/oversight module, seeing as we have consensus for adding both. Would appreciate feedback on what all options the dialog box should contain and other stuff. SD0001 (talk) 16:10, 19 November 2018 (UTC)

Why is there no role account for administrators for revision deletion requests, like User:Oversight? In its absence, it is only possible to support copyvio-revdel requests for which we have a template. I don't see how custom revdel requests can be supported since I don't know of any easy way to send emails externally or access the IRC using javascript. SD0001 (talk) 17:15, 19 November 2018 (UTC)
I now see that User:Enterprisey/cv-revdel.js works delightfully for copyvio-revdel tagging, providing an interactive interface on the page history for selecting the oldid's that the template requires as parameters. Twinkle's form-based layout is clearly not the best way for copyvio-revdel tagging, as digging up the diffs and copying over the oldids is rather cumbersome. Enterprisey's script does the job much better. Hence I guess it'd be better to focus on a module solely for oversight requests. SD0001 (talk) 18:30, 19 November 2018 (UTC)

The initial version of Twinkle oversight module is at User:SD0001/twinkleos.js. To install, please add importScript('User:SD0001/twinkleos.js'); //[[User:SD0001/twinkleos.js]] to your common.js page (that is, until it gets added to standard Twinkle). Feedback is welcome, especially on the options menuu, and default contents of the email subject and body fields that need to improvised. SD0001 (talk) 07:46, 21 November 2018 (UTC)

@Cabayi, Legacypac, Hasteur, SoWhy, PamD, Diego Moya, TonyBallioni, Train2104, M.R.Forrester, FlightTime, Chris troutman, Apap04, Primefac, John from Idegon, Timothyjosephwood, Jiten Dhandha, and Sam Sailor: Feedback? SD0001 (talk) 07:58, 21 November 2018 (UTC)
Please note "Send email" button will send the email to Oversight team. So don't click on it if you're just testing. If you wish, you can copy the code to your userspace page, install it and set the email target to yourself for sending test mails. SD0001 (talk) 08:14, 21 November 2018 (UTC) For now, I have reset email target to mw.config.get('wgUserName'), so that any test emails you send will go to yourself. 08:50, 21 November 2018 (UTC)
@SD0001: Heya! Thanks for working on the script. I did a brief test and it appears to be working all right - the simple text fields are quite neat. The only little trouble I ran into was the "OS" option not appearing in the drop-down for Twinkle sometimes. Refreshing the page a couple of times seems to solve that. My knowledge of scripts and computer in general is quite limited, so maybe it's just a browser issue on my side? Jiten talk contribs 11:53, 21 November 2018 (UTC)
@Jiten D: You may also see that the OS option appears at different position every time. Such issues are due to the order in which JS code is invoked, which I myself don't fully understand. Such issues would automatically disappear when this gets added to the Twinkle standard installation. SD0001 (talk) 13:33, 25 November 2018 (UTC)
@SD0001: Thank for the ping. I also added a linkback for use purposes, you can remove it you want to. Thanks for doing this, I'll let you know if I have any issues. - FlightTime (open channel) 18:38, 21 November 2018 (UTC)
First pass looks nice, SD0001, but can I complicate your life a bit and suggest a different tack? Right now, the form provides the page but is otherwise blank; editors will have to manually collect and add diffs, links, etc. just as they must currently. In short, this saves a few clicks (WP:OS->email) and has a sleek Twinkle interface. What would be really neat/helpful would be one or both of two things: on diff pages, pick up the diff link and username; and on history pages, allow for selecting of multiple diffs. The former is presumably easier. What would be good to avoid would be emails with generic text ("Requesting removal of personal information from User:Amorymeltzer") without more context — that'd save follow-up emails or time spent digging through page histories. ~ Amory (utc) 20:03, 21 November 2018 (UTC)
@Amorymeltzer: On diff pages, pick up the diff link   Done (will update the script soon), but username? Of what use is the username when you have the diff link? On history pages, allow for selecting of multiple diffs -- that sounds quite difficult to me. How are you thinking of doing that? SD0001 (talk) 20:52, 21 November 2018 (UTC)
There. Now a link to the page is also provided. If module was invoked from a permalink / diff page, the link to this is also provided. If invoked from article history, with any two revisions selected (via the radio buttons), a link of a diff comparing those revisions is generated. I am quite busy for 3 weeks from now, so I plan to undertake further improvements after that. SD0001 (talk) 22:19, 21 November 2018 (UTC)
I installed the script but I see no interface for this, either on an history tab or a diff page. Please advise. Chris Troutman (talk) 18:20, 23 November 2018 (UTC)
Do you not see the "OS" tab in the Twinkle dropdown menu? SD0001 (talk) 13:33, 25 November 2018 (UTC)
Nope. Chris Troutman (talk) 00:19, 27 November 2018 (UTC)

Bug for CSD C1 (Empty Categories)Edit


I tag a lot of empty categories from the Database list and even though the "Notify creator if possible" box is checked, there is rarely a deletion notice put on the category creator's talk page. I don't have this problem with any other CSD criteria, just C1. One editor was particularly annoyed because an empty category was deleted after 7 days and they did not receive a notice. The category ended up being recreated (as it was no longer empty) but I said I'd follow up and try to find out what the glitch was with CSD C1 tagging with Twinkle. Any ideas? Liz Read! Talk! 23:33, 22 May 2019 (UTC)

Hi Liz, your Twinkle setting takes precedent over the checkbox at the CSD dialogue. To rectify the issue you have to allow the notification via the settings page. You can do so by accessing Wikipedia:Twinkle/Preferences and then look for "Notify page creator only when tagging with these criteria:" section and check the box for "C1" and/or any other you like. – Ammarpad (talk) 09:26, 23 May 2019 (UTC)
Yup! Liz, if you mouse over the question mark after the "Notify creator if possible" option, you'll see that it specifies that you must have the box checked AND the respective criterion selected in your Twinkle preferences. You haven't customized this from the default, which does not include C1. Checking that box as Ammarpad suggested should do the trick. ~ Amory (utc) 16:28, 23 May 2019 (UTC)
Just seeing this message now, Amorymeltzer. I thought notification was the normal behavior for CSD tagging EXCEPT for C1 where I have this notify box ticked but it never posts a message to the category creator. Because there are a small group of editors who create quite a lot of categories, I sometimes don't want to bombard their talk pages with a great deal of CSD tags but I would prefer that individual editors who have created a single category would get notified. In fact, there was a complaint on ANI about me last month because I placed a CSD C1 tag on an empty category and deleted the categoory 7 days later and the creator was never notified and he was upset. Do you know why Twinkle has this one glitch? Thank you. Liz Read! Talk! 00:08, 5 June 2019 (UTC)
(I moved the above comment from AN ~ Amory (utc) 00:18, 5 June 2019 (UTC))
@Liz: When you go to WP:TW/PREF and scroll to "Notify page creator when tagging with these criteria" is the box for C1 checked? ~ Amory (utc) 00:18, 5 June 2019 (UTC)
Thanks for the advice, Amorymeltzer and Ammarpad. I see about changing this preference. Your knowledge is much appreciated! Liz Read! Talk! 23:43, 8 June 2019 (UTC)
Okay, I followed your instructions. I don't think I had looked at Twinkle preferences since I set it up years ago. For some reason, I had all of the CSD criteria checked EXCEPT for C1 was not a bug, it was my fault! Back then, I must have been thinking that there are a few editors who take care of a lot of Wanted Category creations and I didn't want to plaster their talk page with CSD messages when a slew of similar categories are tagged. So, I don't know if I UNCHECK the notify box on Twinkle notice, if my Preferences will rule over the immediate tagging choices? I had not remembered that there are such a great number of variables on the Twinkle Preferences. Thanks again for helping me out. Liz Read! Talk! 23:55, 8 June 2019 (UTC)

Double signutureEdit

When I am placing talk back templates and want to leave an additional message in the optional message section I often sign that optional message as a habit, but when I publish it places 2 signatures, (an example can be seen here), can a change be made so that twinkle automaticly removes a duplicate signature if you accidently insert (similar to Reply link). Thanks, SSSB (talk) 19:18, 25 May 2019 (UTC)

Previously Wikipedia_talk:Twinkle/Archive_41#Double_signature ~ Amory (utc) 19:41, 30 May 2019 (UTC)
Amorymeltzer, yes, that was me about user warning template. Could you do the same for Talkback. Thanks, SSSB (talk) 19:44, 30 May 2019 (UTC)
Yes, it's on my todo list. FWIW the tooltip when you hover over the question mark says it will add a signature for you, so that might be helpful as a reminder! ~ Amory (utc) 20:00, 30 May 2019 (UTC)

Removing the orphan templateEdit

I know that it's more traditional for me to come ask for "just one more" template in Twinkle, but today I'm asking that you please remove one:

Per Wikipedia:Village pump (idea lab)/Archive 29#Idea - bot to tag orphans, adding the {{orphan}} tag does not seem to be a valuable use of editors' time (either the time of the editor who is adding the template or the time of the multiple editors who review that edit), and its addition should therefore be permitted but gently discouraged. Having any template in Twinkle tends to encourage its use, so I request that you take it out of Twinkle.

Thanks, WhatamIdoing (talk) 19:52, 27 May 2019 (UTC)

I'm pretty sympathetic to this, but I'm not seeing an actionable consensus there. There's also the older Wikipedia:Village_pump_(policy)/Archive_138#Orphans, which might help the argument but muddies the water a bit with its focus on a timeline. ~ Amory (utc) 09:48, 15 June 2019 (UTC)

June 2019 Twinkle updates, features, and behaviors (2019-06-05 @c0e100a)Edit

The latest update brings a number of major improvements to the tagging module from User:SD0001, such the ability to remove tags from articles, a quick filtering system, and a status displaying how many tags you are adding and removing. Also included are a new system for sysops to notify users when speedy deleting their pages, hiding of rollback/revert/etc. links for pages you can't edit, easier selection of warning templates, and batch-deletion of subpages. Plus a number of bug fixes as well as the usual improved handling and functionality. Changes not otherwise attributed were made by User:Amorymeltzer.

  • tag: (All listed changes to tag module by User:SD0001)
    • Add ability to untag and remove templates from articles (485)
    • Group existing tags into {{multiple issues}} when adding tags (485)
    • Add quick filtering functionality for article tags (647)
    • Add status text next to Submit button (e.g., Adding 1 tag; Removing 2 tags) (648)
    • Place new tags under {{AfDM}} (642)
    • Fix long-standing bug where selected custom tags would be unselected if changing between alphabetical and categorical display of tags (653)
  • csd: New option for sysops to notify creator upon deletion, check out your Twinkle preferences to customize when users are notified. Defaults are the same as tagging notifications. (563)
  • revert/rollback:
    • Only add links if the user has necessary perms to edit the page (632)
      • Reverted for contributions, see below
    • Don't create rollback links if the page only has a single revision (630)
    • Fix bug if user selected "Do not show page content below diffs" in their preferences (628)
  • warn:
    • Improved ability to search and find user warnings (just like with deletion sorting for AfDs) (641, User:SD0001)
    • Clicking user talk links on diffs will autofill the article parameter for warning users (it will not auto-open the warning menu if you've selected that) (626)
  • prod:
    • Wait three days before issuing BLPPROD alert if not in BLP cat (610)
    • Detect prior XfDs using templates on talk page rather than just existence of AfD discussion, allows checking for prior MfD and FfD rather than just AfD (637)
  • xfd:
    • Automatically select "Wrap deletion tag with " if page carries {{subst only}} (639, User:SD0001)
    • Fix removal of already-present AfD tags (650)
  • batchdelete: Allow deletion of subpages (581, User:SD0001)
  • arv: Remove tab from user's own pages (622, User:DannyS712)

This section should serve as a catching ground should anything not work properly or if any new bugs crop up, as well as for any feedback or suggestions. As always, input is welcome at the GitHub repo as well. ~ Amory (utc) 15:23, 5 June 2019 (UTC)

Technical Morebits changesEdit

Also, for the more technical folks, there have been a number of changes to the Morebits.js library, briefly noted below:

  • Rename lookupCreator to lookupCreation, also include timestamp (User:Amorymeltzer)
  • Add getUnchecked, pair of getChecked (User:SD0001)
  • Add Morebits.pageNameRegex to create first-letter-case-insensitive regex (User:SD0001)
  • Allow post processing function in batchOperation (User:SD0001)
  • Trigger click event in checkboxShiftClickSupport (User:SD0001)
  • Remove Morebits.wikipedia and Morebits.bytes (User:SD0001)

Additionally, the Twinkle gadget now loads jquery.chosen. Siddhartha Ghai and DannyS712 (and Abelmoschus Esculentus fwiw), you may want to change any instances of lookupCreator with lookupCreation, although the former should continue to work for the time being. ~ Amory (utc) 15:24, 5 June 2019 (UTC)

Nice work, Amorymeltzer and SD0001! Searchable tags and warnings is something I've wanted for a long time - I spend so much time peering through twinkle menus looking for the right tag or warning.. Galobtter (pingó mió) 18:07, 5 June 2019 (UTC)

Bold talk links on diff pages?Edit

The new changes sound great! Was it deliberate to make talk page links on diffs bold, as reported at Wikipedia:Village_pump_(technical)#Talk_pages_bolded_in_diff_view, or is this a bug? the wub "?!" 19:52, 5 June 2019 (UTC)

Thanks, replied there! Intentional, but perhaps undesired. ~ Amory (utc) 20:13, 5 June 2019 (UTC)
I think the bold is good for indicating that the link has an enhanced purpose. But whether it ultimately ends up bold or not, thank you very much for implementing the extremely useful functionality. MANdARAX  XAЯAbИAM 21:35, 5 June 2019 (UTC)
Is there some way I can shut off the bolding? It's getting in the way of my work. Thanks, — Diannaa 🍁 (talk) 14:08, 8 June 2019 (UTC)
@Diannaa: Add { font-weight: normal !important; } to your common.css. Though I too disagree with this bolding and it should probably be reverted for all users. SD0001 (talk) 15:32, 8 June 2019 (UTC)
Thanks, I will do that, exactly what I need. — Diannaa 🍁 (talk) 15:41, 8 June 2019 (UTC)
@Diannaa: Don't sweat it, I'll take care of it in a moment. There was some initial feedback it was undesired so I was waiting to see if there was any more discussion, but consensus seems firmly against the bolding. ~ Amory (utc) 00:23, 9 June 2019 (UTC)
Should be gone (also, wow, sorry, just now realizing your timestamp was nine hours ago...) ~ Amory (utc) 00:43, 9 June 2019 (UTC)

Checking ability to edit each page: Too many values supplied for parameter "titles". The limit is 50Edit


Since the changes, twinkle rollback links no longer load for me on contribution pages. They do load on diff pages. Checking the console gives me the error above, which seems to implicate some "Morebits" code if I try to track it down. That error does not appear on diff pages, where the rollback links load properly. More than that I don't know what to tell you, but if you need any more info please ask. I did try disabling all other scripts, but the issue persists even then. Thanks. -- Begoon 02:02, 6 June 2019 (UTC)

  • Ah - adding - if I display only 50 contribs per page then the links do appear, and the error goes away - more contributions per page than that then they don't appear. Perhaps that helps to narrow it down? -- Begoon 02:17, 6 June 2019 (UTC)
  • Further experiments show that, as the error message I suppose suggests, it's actually the number of different page titles in the displayed list that governs whether I get this error and not the selected number of contributions per page. For instance, if the list of 100 contributions per page contains 50 or less actually different page titles (i.e. there are multiple edits to the same page(s)) it will display with the rollback links, without error. If any contribution listing page, of whatever length, contains over 50 different page titles it will generate the console error and no twinkle rollback links. I hope that makes sense... -- Begoon 06:27, 6 June 2019 (UTC)
    Yup, that's 100% right Begoon. The latest update included a change where Twinkle checks if you can actually edit the page before loading rollback/revert links. The API that allows that check is limited to 50 pages for non-sysop users, which is why you're seeing that. I've reverted that change for now, sorry for the annoyance. Some discussion on github as well. ~ Amory (utc) 09:43, 6 June 2019 (UTC)
    No problem. Thanks for the quick response, and for all the great work you do on this indispensable tool. Cheers. -- Begoon 09:54, 6 June 2019 (UTC)

User warning dialog dropdown selectorEdit

The user warning dropdown is virtually unusable now. Items are listed by the esoteric template names making it difficult to find the appropriate warning. The previous formatting has been deeply ingrained for years and was working without issue, as far as I know. What is the case for making these specific changes?- MrX 🖋 12:55, 6 June 2019 (UTC)

MrX, do you not see the search box in the warning dropdown, which makes the templates easier to find? Items were listed by the "esoteric" template names all the way till March of this year, when the {{uw- prefixes were removed to try make the menu more keyboard-accessible. However, now with the addition of the search box, there is no longer a case for removing the deeply-ingrained-for-years {{uw- prefix, so they have been reinstated. SD0001 (talk) 13:28, 6 June 2019 (UTC)
Yes, SD0001 I see the search box. That may make templates easier to find for people who like to type into search boxes, but for editors who frequently use the warning function and who want to scroll to a warning's familiar location, it makes it considerably more difficult. If the template names are needed, put them behind the descriptive text in light gray so that they don't confuse the humans. Were these change discussed with the community at all? If I'm searching a list, the type of warning us what I'm looking for. I'm not looking for a description, or the name of a template combined with Template:Uw- - MrX 🖋 14:08, 6 June 2019 (UTC)
I agree with MrX. I've been doing countervandalism for years and I don't like changes to the interface that make it harder for me to navigate the tool in the manner in to which I am used. This is why this community keeps killing Flow and other bad ideas. Please give me an option to make the drop-down like it was. Chris Troutman (talk) 14:13, 6 June 2019 (UTC)
I see that the issue is that the density of items in the new select interface is much lesser, thus requiring more scrolling to get to the templates. This also seems to be causing the {{uw- part to stand out more than it used to in classic menu. I'll provide a preferences option to opt out of the new new interface. SD0001 (talk) 14:43, 6 June 2019 (UTC)
Density could also be achieved with some simple CSS inre padding. ~ Amory (utc) 14:58, 6 June 2019 (UTC)
Thank you.- MrX 🖋 15:12, 6 June 2019 (UTC)
Having read through this (thanks for the link Amory), I agree that the reduction of density is an issue. I'd be grateful for the option to disable this in Twinkle settings I had a look for it just now, but didn't see it - if it's already there, could you point me at it? Cheers GirthSummit (blether) 15:46, 6 June 2019 (UTC)
Not yet, but soon! SD0001 was fast. ~ Amory (utc) 15:48, 6 June 2019 (UTC)

───────────────────────── @MrX, Chris troutman, and Girth Summit: There should now be an opt-out user preference in your twinkle preferences, look for Use the non-searchable classic select menu. Credit to SD0001 for the quick code. ~ Amory (utc) 18:59, 6 June 2019 (UTC)

Thank you, but was the template code listed before or am I just noticing it now? - MrX 🖋 19:03, 6 June 2019 (UTC)
The full template names have been there for over a decade. As mentioned above, the uw- portion was removed just a few months ago to try and solve something that the new menu does much more elegantly. ~ Amory (utc) 19:39, 6 June 2019 (UTC)
Thanks for the ping Amory, and to SD0001 for making the change so quickly. It looks like the density issue has been addressed in the default view now however: I'm able to see the same number of options as I was in the past, which was my principal annoyance, so I'm happy with the new look now. Cheers! GirthSummit (blether) 08:33, 8 June 2019 (UTC)

Some inaccurate field descriptions in user warning menuEdit

A few of the warning options have an incorrect prompt for the extra information field (the field below the template name where you usually put the name of the article you're warning about, not sure what the correct name for the field is). I haven't checked thoroughly, but the autobiography template prompts for "Optional username that was reported (without User:)" instead of the article name (in fact, it looks like all of the single-issue notices have that problem), and the bad username template prompts for "Linked page" instead of a description of the problems with the username. creffett (talk) 14:51, 6 June 2019 (UTC)

Thanks — reported on github, and I made a potential fix live, should go into action in 5-10 minutes. ~ Amory (utc) 15:00, 6 June 2019 (UTC)
Awesome, thank you! creffett (talk) 19:05, 6 June 2019 (UTC)

Long previews overlap and block "Submit" buttonEdit

Hello, I hope it's OK to post some additional bug feedback here: when previewing long user warnings (for example uw-coi or other long messages), the "Preview" display of such long messages overlaps and blocks the "Submit" button at the bottom of the window. More precisely, the underlying window stays small and doesn't extend its size to accomodate longer messages in the preview field. Currently, the only way to submit warnings with a long message text is to avoid pressing the "Preview" button at all. GermanJoe (talk) 17:28, 8 June 2019 (UTC)

#665. A known bug. Until a fix is deployed, please resize the dialog by dragging the bottom-right corner, that will make the submit appear. SD0001 (talk) 17:47, 8 June 2019 (UTC)
Thank you for the information. GermanJoe (talk) 17:56, 8 June 2019 (UTC)
 Y Fixed a few days ago. SD0001 (talk) 18:30, 14 June 2019 (UTC)

Batch Deletion QuestionEdit

I have another Twinkle question. I'm considering utilizing batch deletion because I have an old computer that is rather slow when I'm moving from tab to tab but Wikipedia:Twinkle/doc#batchdelete doesn't provide much help. My question is in the section in the pop-up that appears states "Pages to delete" with Select All or Deselect All as the alternatives. What I would think I'd see is a list of open tabs and then checkboxes so I could select the open pages to delete.

But there is no list of pages to select from. Soooo, would Select All delete every page that I have open in a tab in this window? Or every page that I have open in all my windows? I'm not going to Select All when I don't know what I'm selecting. As the module states, batch deletion could cause massive disruption. I'm hoping because I see D-batch used frequently among admins that someone can answer my question. And if it involves going back into my Twinkle preferences again, I will feel rightly ashamed. Any help? Thanks in advance. Liz Read! Talk! 23:10, 10 June 2019 (UTC) "

Good Lord. Batchdelete is for zapping all pages that are linked from the page you're using the script from. It may be a normal page or a category or a Special:PrefixIndex page. Pages you're about to delete will be listed in the 'Pages to delete' section, so don't worry. If there are no pages in the list, that means you're using it on page which doesn't link to any other page. SD0001 (talk) 17:09, 11 June 2019 (UTC)
Return to the project page "Twinkle".