Talk:Main Page

Badminton module

Hi there. Could I get some help for improving. I try to use these codes, but there are some columns with zero, which should be not shown, as the data might not be available. So I expect the column would be: Pos, Team, Pld, W, L, MF, MA, MD, Pts, Qualification (for uncomplete table, activated by "point_for_against_style=none". Any help would be appreciated. Regards. Medelam (talk) 13:49, 19 October 2021 (UTC)[reply]

Looks like you want, which removes the header columns. However there doesn't seem to be code to disable the data rows in . I've changed your example (above) and will I'll see if I can get it to work in the sandbox. — Jts1882 | talk 14:32, 19 October 2021 (UTC)[reply]

@Medelam: Is the above now what you require? — Jts1882 | talk 14:41, 19 October 2021 (UTC)[reply]

@Jts1882: Yes, that is exactly what I want. Appreciate your effort. Thank you and regards. Medelam (talk) 14:44, 19 October 2021 (UTC)[reply]

I've put it live. The header code was also hiding the points columns if the games columns were hidden, so I've done the same with the country rows for consistency. So |point_for_against_style=none is redundant when |game_for_against_style=none is set. — Jts1882 | talk 15:18, 19 October 2021 (UTC)[reply]

Looking for help from a Python dev to help getting ReFill to build and run

I volunteered to take over maintenance as the original developer was no longer interested/able to do so. I am set up with Toolforge access via PuTTY etc. I'm having difficulties getting the code to build and run locally on my dev machine. I could really do with a Python dev to help me deal with NPM versioning issues (breaking changes in dependencies). Ideally, it would be someone who would be willing to be around longer than just to get me going, i.e. to field occasional subsequent questions. Hopefully, Curb Safe Charmer (talk) 16:54, 19 October 2021 (UTC)[reply]

@Curb Safe Charmer: Hey! I got that running locally not that long ago Template:P what's broken? ~TheresNoTime ^{(to explain!)} 17:04, 19 October 2021 (UTC)[reply]

Replied on TheresNoTime's talk page. Thanks - this is hopefully the help I need - if not, I will post again here. Curb Safe Charmer (talk) 20:06, 19 October 2021 (UTC)[reply]

Just a note, if this gets into Pythonic Madness I may have to poke someone like Tamzin ~TheresNoTime ^{(to explain!)} 20:09, 19 October 2021 (UTC)[reply]

Funny white bars in history previews, using green-on-black gadget

This seems to have started today. When I point my mouse at "hist" on my watchlist the pop-up shews more-or-less as usual, but with vertical white bars between cur prev | time | username | section. You can see a picture of it here. They are not visible if I switch the gadget off. DuncanHill (talk) 19:08, 19 October 2021 (UTC)[reply]

@DuncanHill: there was an update to Wikipedia:Tools/Navigation popups today - is that what you are using? Perhaps there is a conflict with something in MediaWiki:Gadget-Blackskin.css. As the former has ~55000 users and the later has ~6400, I'd rather someone propose a change to blackskin then rollback navpops though. — xaosflux ^Talk 19:20, 19 October 2021 (UTC)[reply]

@Xaosflux: Yes, Navigation Pop-ups. DuncanHill (talk) 19:24, 19 October 2021 (UTC)[reply]

Apparently blackskin.css overrides the table background, and the cell background, but not the background-color of the table rows —TheDJ (talk • contribs) 19:24, 19 October 2021 (UTC)[reply]

Template:Replyto we can just add this into the table section of the blackskin.

table tr { 
    background-color: #000000!important;
    color: #00dd00!important;
}

—TheDJ (talk • contribs) 19:34, 19 October 2021 (UTC)[reply]

@TheDJ: thank you for the markup; @DuncanHill: I updated blackskin, please check in about 5 mins? — xaosflux ^Talk 20:44, 19 October 2021 (UTC)[reply]

@TheDJ: and @Xaosflux: Thank you, works as expected now. DuncanHill (talk) 20:59, 19 October 2021 (UTC)[reply]

wpTextbox1 equivalent in 2017 wikitext editor

What is it's equivalent? I don't find the element anywhere in the page and thus almost no user script in Wikipedia:User scripts/List#Editing doesn't work for me. The Wikipedia:User scripts/Guide seems to be written for the 2010 editor and isn't helpful for me in editing mode, when I try to develop a script on my own. Thanks for any help! — DaxServer (talk) 13:49, 20 October 2021 (UTC)[reply]

wpTextbox1 is present alright for the 2017 wikitext editor. You should use jQuery.textSelection API for textbox interactions as they'd work independently of the type of source editor. – SD0001 (talk) 15:06, 20 October 2021 (UTC)[reply]

@SD0001 Thanks for the reply. I must have been doing something so wrong!! — DaxServer (talk) 15:21, 20 October 2021 (UTC)[reply]

Proposal to turn the DYK helper into a gadget

Template:Atop This proposal arises out of ongoing efforts to simplify the process of making DYK nominations so that newcomers are able to complete it more easily (see here and here). Currently, one of the first obstacles is installing the DYK helper script, which requires editing your js page. If the helper were a gadget, all it'd require to activate is going to the settings page. The helper is very widely used and trusted (kudos to maintainer SD0001), so I propose turning it into a gadget. (Per here, this is the place to do that.) {{u|Sdkb}} ^talk 19:48, 18 October 2021 (UTC)[reply]

Support as proposer. {{u|Sdkb}} ^talk 19:48, 18 October 2021 (UTC)[reply]
Support. The process of posting a Did you know nomination is currently very manual, which can put off people from submitting them, and automating it makes a lot of sense. I think this helper script is a good step forward with this, but asking (potentially new) editors to install it in their individual javascript pages is very off-putting and very technical: it becomes a lot easier if it's just an option to turn on in their preferences. Thanks. Mike Peel (talk) 19:55, 18 October 2021 (UTC)[reply]
Support In general, the entire DYK review process and feedback/comments also feels way too manual and different from talk page discussions which I would have expected. The less manual, the better overall! ~ 🦝 Shushugah (he/him • talk) 22:52, 18 October 2021 (UTC)[reply]
? (1) @SD0001: are you good with this? (2) @Sdkb: confirming this would be for opt-in, correct? — xaosflux ^Talk 23:21, 18 October 2021 (UTC)[reply]
For (1), see here. For (2), yes. {{u|Sdkb}} ^talk 23:25, 18 October 2021 (UTC)[reply]
Support - I'm all for simplifying any process, especially if it helps new users. — Maile (talk) 23:29, 18 October 2021 (UTC)[reply]
Support turning this excellent script into a gadget —valereee (talk) 00:01, 19 October 2021 (UTC)[reply]
Support. I do not know the effort that goes into creating a gadget, but, I support this action that will greatly simplify the act of submitting a DYK nomination. Actually on that note if there is a way to simplify any other main page nomination (ITN nomination comes to mind) as a part of the same submission gadget, that would be welcome too. I am adding some ITN Admins just as an fyi. cc @Stephen, Spencer, PFHLai, Masem, and MSGJ: — Preceding unsigned comment added by Ktin (talk • contribs) 00:07, 19 October 2021 (UTC)[reply]
@Stephen, Spencer, PFHLai, Masem, and MSGJ: as a courtesy to Ktin above. --Izno (talk) 01:08, 19 October 2021 (UTC)[reply]
I'm all for more automated tools to help make these sections easier to use. Don't know enough about the DYK side of things to specifically comment there. Spencer^T•C 02:21, 19 October 2021 (UTC)[reply]

Glad to see more tools and new ways to contribute. :-) --PFHLai (talk) 10:23, 19 October 2021 (UTC)[reply]
Some non-blocking comments to this action (overall I want all the widely-used scripts to be gadgets): 1) I dislike the use of morebits.js. I am sure it is convenient, but it sure is so 2005 in looks. :^) 2) The name should be indicative of its purpose if possible; DYK "helper" is not. It appears to be exclusive to nominations, so, "DYK nominator" or even "DYKN.js" would be preferable. --Izno (talk) 01:03, 19 October 2021 (UTC)[reply]
I like the idea, but installing a gadget is still one more step than necessary - I imagine we could use a withJS link here? That way you'd just click on a button "submit a DYK" on the DYK page (that's probably the precise place where people have the idea to submit their article, after all) and have the form immediately open. That would also eliminate any need to hunt down the "DYK" menu item or link. It would require a little coding and add one form field (you'd need to write the name of the article), but I'd be happy to help out and I think the extra inconvenience is worth it. A gadget would still help power users who submit lots of DYKs, but I would imagine they would be experienced enough to be able to install a user script (especially with script-installer). (I also feel like the gadget list is getting a little long, but that's a really, really tiny concern.) If we go ahead with a gadget nonetheless (which I'm not opposed to! just proposing another solution), I agree with what Izno said about naming. For Ktin, I would absolutely be in favor of introducing forms for those other processes. Enterprisey (talk!) 02:20, 19 October 2021 (UTC)[reply]
Thanks @Enterprisey: and apologies for the digression. I must admit I know the least about gadgets and user scripts. But, what is the best way to take this conversation forward? The folks above are the real gurus of the ITN page. Happy to help coordinate. Ktin (talk) 02:46, 19 October 2021 (UTC)[reply]
@Ktin, well, you're in luck! I just made Wikipedia:Workflow improvements, so we could talk further over there. Enterprisey (talk!) 10:10, 19 October 2021 (UTC)[reply]

Is there something blocking having the gadget accessible from withJS? Probably means a little modification (autofill versus not of the page of interest), but that doesn't seem like a big deal. Izno (talk) 03:09, 19 October 2021 (UTC)[reply]
Yes, that's the only thing blocking it as far as I'm aware. Not a big deal, yeah. Enterprisey (talk!) 03:21, 19 October 2021 (UTC)[reply]

The use case for this seems to be primarily using a single form entry for a task - as such I'm much more in favor of ?withJS if it will work. The primary benefit for end users is that they won't have to go enable anything - they would just get a button to click on. The downside (?) is that they would need to navigate to the page and push the button as opposed to say adding this to a tool menu on their interface. — xaosflux ^Talk 15:01, 19 October 2021 (UTC)[reply]

That's precisely what I told Sdkb when they approached me (see User_talk:Mike_Peel#DYK_nomination_instructions). But it will require extensive changes and is not something I see happening in the near future. This script uses Morebits.quickForm that's designed to work within modal windows. A full-page form would render oddly with quickForm (eg. you can't even limit the width of the textareas, they'll spread across the page). While morebits is a good framework for complex forms within small dialogs (which OOUI is really lousy at), for a full-page form it's better to use OOUI. There are lots of UI controls in this script (for handling multiple hooks, multiple nominators, multiple articles, ...) which would likely require custom OOUI widgets. Also, the prose size calculation relies on the article being open (it can be tweaked to load the article html via the API, but then what with the user being able to change the article ...). – SD0001 (talk) 16:17, 19 October 2021 (UTC)[reply]
Sure, the "proper" way would be to convert it to a full-screen form, but honestly I don't think that's a requirement; it'll still work perfectly fine as a modal form, I'm guessing, even if it'll look a little weird. (Please correct me if I'm wrong.) For the prose size, yes, that's inconvenient, but I'd imagine people would use the dedicated widget for that if they do it very often. Enterprisey (talk!) 22:29, 19 October 2021 (UTC)[reply]
Hm. I think it would be semi-professional to open an all new page on which a modal pops up. But regarding the conversion to full-screen form, I think I may spoken too soon. Let me take a shot at that first – it's just that quickForm hasn't ever been used outside a modal (WP:TWPREF looks similar to other Twinkle windows that use quickForm, but actually it uses HTML built from the ground up!). It shouldn't be too hard to do some refactoring and have everything fit into a fixed-width div. Might need a couple of morebits patches. – SD0001 (talk) 09:31, 20 October 2021 (UTC)[reply]

Nevertheless, I suppose one day it could be rewritten (maybe as part of WP:Workflow improvements) – which brings to the other point: when https://gerrit.wikimedia.org/r/c/mediawiki/extensions/Gadgets/+/730684 is merged (likely, since it just cleared a security review) it would be possible to load gadgets via URL – in a way that's quite more performant than the current withJS trick (resourceloader minimisation, caching, load being requested before page is ready, etc – basically all the advantages that gadgets have over user scripts). When both of these happen we can convert this to a hidden gadget and have it load only by URL. – SD0001 (talk) 16:26, 19 October 2021 (UTC)[reply]
Awesome! Enterprisey (talk!) 22:29, 19 October 2021 (UTC)[reply]

It required some refactoring, but this is {{done}}. I posted a note on WT:DYK#DYK-helper_script_improvements_and_auto-loading which has instructions on testing it out. cc @Sdkb and Enterprisey:. – SD0001 (talk) 14:22, 21 October 2021 (UTC)[reply]
Comment - I'm not entirely sure which part of the process this proposal is covering, but noting that DYK already has a fairly intuitive process at WP:DYKNOM where you fill in the name of your article and off you go. It seems like the hard part about that is that you have to then go and edit the newly created DYK nom template, and then also transclude the nomination on the appropriate page. So I think we should be focusing our efforts on automating the latter two steps to complete that process, while keeping the ease-of-use of the form at WP:DYKNOM. The above-mentioned solution, which as far as I can tell involves either installing a JS script or fiddling around with your settings, is the very opposite of an ease-of-use solution for newcomers. Cheers — Amakuru (talk) 08:07, 20 October 2021 (UTC)[reply]
@Amakuru This only creates the template, but does not actually link/transclude it anywhere which was confusing for me. Because I once created the template and expected it to transclude. I also noticed the preload template doesn't automatically autopopulate the title parameter, but I can fix that directly. ~ 🦝 Shushugah (he/him • talk) 09:52, 20 October 2021 (UTC)[reply]
@Shushugah: yes, this is my point. Rather than creating an entirely new tool, which requires users to install something on their profiles, the page I mention should be expanded and updated so that it does all of the steps rather than just one of them. Either that, or have a bot do the heavy-lifting, which is what happens at WP:GAN - an example of a good user-friendly process IMHO. Cheers — Amakuru (talk) 09:59, 20 October 2021 (UTC)[reply]
I boldly edited Template:T:TDYK/preload to autopopulate the article name. Have a look ~ 🦝 Shushugah (he/him • talk) 10:19, 20 October 2021 (UTC)[reply]

To clarify, when @Shushugah says This only creates the template, ... they are talking about the inputbox at WP:DYKNOM, not the script. – SD0001 (talk) 16:15, 20 October 2021 (UTC)[reply]

@Amakuru DYK-helper automates all of those steps. – SD0001 (talk) 16:14, 20 October 2021 (UTC)[reply]

Template:Abot

Lets talk about main TITLE EDIT TEST

Main? Mgrover(WMF) (talk) 06:49, 20 May 2013 (UTC)[reply]

test Testuser451716 (talk) 18:10, 27 April 2020 (UTC)[reply]

Let's talk about main, baby Let's talk about you and me Let's talk about all the good things And the bad things that may be Let's talk about main Let's talk about main

Jdlrobson (talk) 17:06, 9 July 2013 (UTC)[reply]

Test discussion on main page, tes tes :) Alangi Derick (talk) 09:18, 24 October 2018 (UTC)[reply]

test 216.37.72.238 (talk) 20:28, 14 December 2020 (UTC)[reply]

test 185.157.15.111 (talk) 18:10, 2 June 2021 (UTC)[reply]

hello 185.157.15.111 (talk) 18:13, 2 June 2021 (UTC)[reply]

test test Cat test Quiddity (talk) 18:52, 5 November 2021 (UTC)[reply]

test 23.93.17.85 (talk) 17:48, 2 March 2023 (UTC)[reply]

My test talk

Talk info Mgrover(WMF) (talk) 06:50, 20 May 2013 (UTC)[reply]

Test Martin Urbanec (talk) 12:31, 2 May 2020 (UTC)[reply]

This is a test. Adding a link feels strange when you're on a desktop machine. The icons in the toolbar aren't all the same size. Whatamidoing (WMF) (talk) 18:46, 5 November 2021 (UTC)[reply]

My talking

And more talking Selenium user (talk) 05:32, 9 July 2013 (UTC)[reply]

`hello, world?` Ppelberg-test (talk) 00:09, 12 December 2019 (UTC)[reply]

@JDlrobson: can you hear me, jon? Ppelberg-test (talk) 00:10, 12 December 2019 (UTC)[reply]

test Majavah (talk) 07:19, 23 July 2020 (UTC)[reply]

Hi，how are you？I am from China，can we make a friend？ 112.99.232.206 (talk) 03:46, 1 February 2021 (UTC)[reply]

heiio 120.221.12.222 (talk) 04:22, 24 July 2022 (UTC)[reply]

heiio 120.221.12.222 (talk) 04:24, 24 July 2022 (UTC)[reply]

Bug 17663

Testing by en:User:cscott.

<s.foo>s.foo</s.foo>

bug 41756

a
b
c

iiiii

d
e

I am Scatman

[sings] 198.73.209.4 (talk) 00:03, 23 July 2014 (UTC)[reply]

@Jdforrester (WMF): are you there? Ppelberg-test (talk) 00:12, 12 December 2019 (UTC)[reply]

Regretably. Let's move this to a specific discussion test page; I've created Talk:Discussion tool test. Jdforrester (WMF) (talk) 17:42, 12 December 2019 (UTC)[reply]

Okay，where are you from ？bro.And what topics would you like to discuss? 112.99.232.206 (talk) 03:50, 1 February 2021 (UTC)[reply]

this is a test msg Martin Urbanec (talk) 18:14, 5 June 2021 (UTC)[reply]

Sent here to translate

I want to translate English articles to Kreyol Ayisien. Am I in the right place? Bfpage (talk) 16:39, 11 June 2015 (UTC)[reply]

Test

@PEarley: SydneyPoore (talk) 21:46, 30 May 2017 (UTC)[reply]

Testing 198.73.209.241 (talk) 00:02, 13 December 2019 (UTC)[reply]

TEST -- Alice 198.73.209.241 (talk) 00:03, 13 December 2019 (UTC)[reply]

i am going to push command enter MMiller Test 01 (talk) 17:52, 23 December 2019 (UTC)[reply]

test Majavah (talk) 07:20, 23 July 2020 (UTC)[reply]

topic

discussion Alice1 (talk) 15:40, 22 January 2021 (UTC)[reply]

okay bro,what topics would you like to discuss 112.99.232.206 (talk) 03:55, 1 February 2021 (UTC)[reply]

test

tests Alice1 (talk) 15:42, 22 January 2021 (UTC)[reply]

test

test Alice1 (talk) 15:43, 22 January 2021 (UTC)[reply]

t

t Alice1 (talk) 15:44, 22 January 2021 (UTC)[reply]

hiii 185.157.15.111 (talk) 18:14, 2 June 2021 (UTC)[reply]

test Testuser451716 (talk) 17:49, 3 June 2021 (UTC)[reply]

hello 185.157.15.111 (talk) 19:17, 3 June 2021 (UTC)[reply]

aaa 185.157.15.111 (talk) 15:31, 23 June 2021 (UTC)[reply]

aa 185.157.15.111 (talk) 15:32, 23 June 2021 (UTC)[reply]

hi 185.157.15.111 (talk) 17:00, 2 August 2021 (UTC)[reply]

hi Yatu (talk) 17:01, 2 August 2021 (UTC)[reply]

I am chinese，hello 120.221.12.222 (talk) 04:23, 24 July 2022 (UTC)[reply]

Bug testing Main Page (with reply tool)

Bug testing Main Page (with reply tool) TestUserEsther (talk) 15:54, 28 September 2021 (UTC)[reply]

Try test

Full of things! Dyolf77 (talk) 17:05, 15 November 2021 (UTC)[reply]

Hello! Yatu (talk) 16:09, 16 November 2021 (UTC)[reply]

Testing

Testing, testing… Yatu (talk) 16:08, 16 November 2021 (UTC)[reply]

MediaWiki:Watchlist-details

Would an Admin please fix it? It is disingenuous about open RFAs, and this project has no Admin Noticeboard infrastructure. Jeff G. (talk) 13:53, 19 February 2022 (UTC)[reply]

Test

All tests TestEsther (talk) 23:27, 25 April 2022 (UTC)[reply]

Also a test. DLynch (talk) 17:13, 13 May 2022 (UTC)[reply]

Even this is a test. DLynch (talk) 17:14, 13 May 2022 (UTC)[reply]

Future comment. ESanders (WMF) (talk) 09:25, 25 August 2022 (UTC)[reply]

@ESanders (WMF): May I borrow your time machine? ;) Jeff G. (talk) 10:46, 27 June 2022 (UTC)[reply]

"4 people in discussion" instead of "4 users in discussion"? Tester Vector TOC 3023 (talk) 14:30, 27 June 2022 (UTC)[reply]

Is there a reason you prefer "users" over "people"? ESanders (WMF) (talk) 17:03, 14 July 2022 (UTC)[reply]

Because in the MediaWiki jargon, the term is "user". Tester Vector TOC 3023 (talk) 13:07, 1 August 2022 (UTC)[reply]

Only two industries call people "users": software development and drug selling. :-P 138.0.8.19 (talk) 18:12, 5 January 2023 (UTC)[reply]

@Lorem ipsum? Tester Vector TOC 3023 (talk) 13:16, 1 August 2022 (UTC)[reply]

Adăugare subiect

Test Add a topic via sticky header. Tester Vector TOC 3023 (talk) 13:15, 1 August 2022 (UTC)[reply]

etwetwet 86.14.36.64 (talk) 14:57, 19 June 2023 (UTC)[reply]

test <1>

test Dreamyjazz (talk) 16:03, 10 May 2024 (UTC)[reply]

test Dreamyjazz (talk) 16:04, 10 May 2024 (UTC)[reply]