Wikipedia talk:Gadget/Archive 2
 | This is an archive of past discussions on Wikipedia:Gadget. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
| Archive 1 | Archive 2 |
How about calling it Wikigets???
I would love to call these accessory gadgets Wikigets. Pls give ur views on this proposal. I think it would be nice to hav a wiki touch. Amartyabag TALK2ME 06:44, 28 April 2008 (UTC)
- Eugh. We don't need "wiki" plastered over everything. This is just a tool to make JavaScript addition easy for code newbies, so let's not try to brand it. Wikipedia's brand recognition is good enough. Nihiltres{t.l} 18:18, 28 April 2008 (UTC)
Twinkle as a Gadget
I've removed Twinkle from the Gadget list temporarily; please see the discussion at WP:AN#Vandal making use of Twinkle. Ral315 (talk) 18:43, 29 April 2008 (UTC)
- I wondered what the hell happened to my other tabs. Hopefully we can get this rectified soon. I added it back manually, but prefer to have as little in my monobook as possible. -- Kesh (talk) 15:27, 30 April 2008 (UTC)
- It has been restored as a gadget. DuncanHill (talk) 09:05, 1 May 2008 (UTC)
Make your own Gadget
Will we ever be able to make our own gadgets? Marshall T. Williams (talk) 22:52, 13 September 2008 (UTC)
- Yes, you can already do that! If you have knowledge of JavaScript and/or CSS, create a gadget as a user script or style sheet (or both). From there, suggest that it be added as a gadget—if you get consensus, it'll be done. {{Nihiltres|talk|log}} 23:48, 13 September 2008 (UTC)
Skin support
I think it would be a good idea to demand that any gadget passing the evaluation should support all skins installed in Wikipedia (including Nostalgia, which I use). NerdyNSK (talk) 10:20, 6 October 2008 (UTC)
Broken comments in CSS gadgets?
I noticed that the instructions on this page state that a header made of "//"-style comments should be added to both JS and CSS files. However, according to the CSS spec only "/* */"-style comments are valid. Should that be fixed? Anomie⚔ 14:49, 16 June 2009 (UTC)
- Which CSS scripts use
//-style comments? The only one I found was MediaWiki:Gadget-Blackskin.css. You're right in that those style of comments do not work in CSS files. Gary King (talk) 15:31, 16 June 2009 (UTC)- That's the only one I see too, but there's also the instructions on WP:Gadget. I decided to be bold and fix that. Anomie⚔ 23:12, 16 June 2009 (UTC)
Gadget-Blackskin
This gadget was added back in January 2008 by Prodego, without any discussion that I can see. Per its description, it provides "a black background with green text on the Monobook skin"; however, if we're going to start having CSS stylesheet gadgets, there are any number of other stylesheets I'd see made into gadgets long before this - including plenty of purely aesthetic ones (rounded corners, anyone?). Can anyone else fill in any of the history on just how this came to be a gadget, and does anyone else have an opinion on whether it should remain a gadget or be removed? 「ダイノガイ千？！」? · Talk⇒Dinoguy1000 09:45, 18 June 2009 (UTC)
- I remember that this was one of the reasons to set up the WP:Gadget page and to start discussing gadgets in a central place before putting them online. One user cared quite a lot of having this gadget installed, while I saw - and still see - it as a candidate to be removed. We still have the normal monobook.js way for the more exotic or crazy userscripts and stylings. It would immensely help if we had a mechanism to see how many active editors have actually checked a certain gadget. Cacycle (talk) 17:23, 18 June 2009 (UTC)
- It was specifically requested by a number of people, I personally don't use it. Prodego talk 17:33, 18 June 2009 (UTC)
- As of March 21, 2009, at least 2000 people were using it. That's more than several other gadgets. --Splarka (rant) 07:23, 19 June 2009 (UTC)
- As far as I can see it shows only the number of accounts that have it checked, not the number of active editors actually using it. It is the kind of simple description gadget that a new and inexperienced user would check just out of curiosity or to see how gadgets work. Cacycle (talk) 12:56, 19 June 2009 (UTC)
- As of March 21, 2009, at least 2000 people were using it. That's more than several other gadgets. --Splarka (rant) 07:23, 19 June 2009 (UTC)
- It was specifically requested by a number of people, I personally don't use it. Prodego talk 17:33, 18 June 2009 (UTC)
- I remember that this was one of the reasons to set up the WP:Gadget page and to start discussing gadgets in a central place before putting them online. One user cared quite a lot of having this gadget installed, while I saw - and still see - it as a candidate to be removed. We still have the normal monobook.js way for the more exotic or crazy userscripts and stylings. It would immensely help if we had a mechanism to see how many active editors have actually checked a certain gadget. Cacycle (talk) 17:23, 18 June 2009 (UTC)
If you want to do a rounded corners gadget, I think that User:Drilnoth/rounded.css is pretty comprehensive, but only for Mozilla browsers. –Drilnoth (T • C • L) 18:24, 20 June 2009 (UTC)
- I wasn't necessarily requesting one, but merely pointing out one that would be in far higher demand (IMHO, of course). 「ダイノガイ千？！」? · Talk⇒Dinoguy1000 19:04, 22 June 2009 (UTC)
Gadget usage statistics
It would help immensely if there was a gadget usage statistic implemented in MediaWiki. Knowing the usage patterns of gadgets would allow to identify rarely used and too exotic gadgets that would be better used as a traditional user script. This would help in maintaining the gadget selection list at a user friendly size and would also help to prioritize gadget development.
I have filed a Bugzilla bug report for this, please see bugzilla:19288. — Preceding unsigned comment added by Cacycle (talk • contribs) 21:43, 18 June 2009
- It might be possible to get this information filtered from the Toolserver similar to that watcher tool. — Dispenser 03:20, 27 October 2009 (UTC)
- This is now available at Wikipedia:Database_reports/User_preferences. Superm401 - Talk 05:03, 4 March 2012 (UTC)
Edit summary gadget
The darn thang didn't work. It did increase the number of characters I could type into the box, and as appeared in the edit summary preview, but when I saved the page, it cut off at exactly 200 chars as normal. [1] That behavior seems worse than useless! Is it possible I did something wrong? • Anakin (talk) 00:38, 27 October 2009 (UTC)
I tried again: [2]. Still caps at exactly 200. • Anakin 20:06, 26 November 2009 (UTC)
- Please contact the maintainer of that gadget and provide full details about your browser and how to replicate it. Cacycle (talk) 09:02, 27 November 2009 (UTC)
Usage-Stats
Hello folks,
I am here at the tech-meeting and a user asked me, if I could generate a gagdet-usage-statistic on the toolserver. Here is the usage of gadgets of all active (=make at least 1 edit in the last 30 days) users.
Have fun, de:User:DaB. 22:23, 15 April 2010 (UTC)
Numbers of install of the Gadget courtesy of the Toolserver administrators. I've added comparison to dewiki from a report done in March. — Dispenser 17:04, 11 September 2010 (UTC)
- Update: I've combined DaB.'s April numbers with the new September numbers. There is a considerable differences in rankings between active and all users. — Dispenser 19:49, 11 September 2010 (UTC)
- Wikipedia:Database reports/User preferences, updates weekly. It's possible to build an adoption graph by collating the revisions. — Dispenser 21:09, 6 June 2011 (UTC)
Discussion at Wikipedia talk:Spoiler may be of interest to gadgeteers
At the moment there is an RFC at the spoiler guideline talk page that may be of interest to scripters who write and maintain gadgets because it's a proposal to make a small change to the layout of the Vector skin, probably to insert a link to the site Disclaimers into the sidebar so that it will be more prominent--currently it's only linked from the page bottom.
I expect that this would be achieved by having Mediawiki:Vector.js inject the link into the appropriate place. This may (or may not) have implications for gadgets that make assumptions about the layout of the vector skin. --TS 13:49, 8 October 2010 (UTC)
Live UTC Clock Wrong
{{editprotected}}
It's 1 hour ahead of time. Could someone fix that? --Σ talkcontribs 02:55, 17 August 2011 (UTC)
- I don't think that can be done from this page, but anyway, somebody must have fixed it: the gadget is showing the right time for me, the same as this. JohnCD (talk) 16:49, 18 August 2011 (UTC)
Updated MediaWiki:Gadget-citations.js
I have updated MediaWiki:Gadget-citations.js so that now it uses protocol relative urls (ie. when logged in with https:// ) it calls toolserver with the same protocol, hence not logging out users who are using a secure login. It works for me, can others please double check. Thanks. — billinghurst sDrewth 07:02, 9 December 2011 (UTC)
Changes needed for definitions in 1.19
To prepare for 1.19, the MediaWiki:Gadgets-definition page should be updated with the page here: User:MarkAHershberger/1.19-gadget-definition. Without these changes, gadgets will stop working because of un-declared dependencies. See mw.util is undefined in MediaWiki:Common.js for more info. — Preceding unsigned comment added by MarkAHershberger (talk • contribs)
- May I asume you tested that each and every gadget is working with ResourceLoader? — Edokter (talk) — 18:39, 16 January 2012 (UTC)
Clock gadget not appearing
Not sure why, but the appearance gadget that shows a UTC clock on the top right area, that allows you to click it to purge a page, is no longer working. I went ahead and disabled it and re-enabled it and it's still not showing up. VegaDark (talk) 21:03, 16 January 2012 (UTC)
- Working now, appears to have been related to this. VegaDark (talk) 22:02, 16 January 2012 (UTC)
MediaWiki:Gadget-dropdown-menus.js: update needed
This gadget should be updated, due to use of the following:
- Legacy globals (wgUserGroups, wgPageName, skin, wgTitle, wgScript, wgEnableAPI, ..)
- Deprecated modules (ajax: sajax_init_object, wikibits: addOnloadHook)
- check out JavaScript deprecation guide and User migration guide
Aside from that I'd recommend:
- Simplify the ajax calls by using
mw.util.wikiScript('api')andjQuery.getJSON(instead of wgScriptPath and sajax_init_object). - Pasting the code through http://www.jshint.com/ and perhaps apply some best practices (you can untick the ones you don't care about on the bottom of the page)
Krinkle (talk) 21:10, 16 January 2012 (UTC)
WhatLeavesHere : useful gadget, especially for admins and spam cleaning
m:User:Krinkle/Tools/WhatLeavesHere is proving useful to me when quickly looking at links on a page when managing spam, or just simply looking at what is linked off a page. Something worthwhile considering as a universal gadget here, or at least for people to consider adding into their common.js file. — billinghurst sDrewth 02:08, 24 January 2012 (UTC)
Gadget creators invited to Berlin hackathon 1-3 June 2012
At the upcoming Berlin hackathon in June, we'd especially like to have conversations with Gadgets developers. Experts will be available to discuss extending functionality with JavaScript, the future of ResourceLoader and Gadgets, the new Lua templating system, how to best use the web API for bots, and various upcoming features and changes. We'd love to have power users, Gadget creators, bot maintainers and writers, and template makers at this event so we can all learn from each other and chat about what needs doing.
Best wishes! Hope to see you there. - Sumana Harihareswara, Wikimedia Foundation's Volunteer Development Coordinator. Please reply on my talk page, here or at mediawiki.org. —Preceding undated comment added 16:25, 16 February 2012 (UTC).
- I'll add more information about this as soon as possible, but there will be travel sponsorships available. Sumana Harihareswara, Wikimedia Foundation Volunteer Development Coordinator 02:59, 12 March 2012 (UTC)
Teahouse gadget
Hey folks,
I've just added a super simple gadget for the Teahouse project's "ask a question" page. I originally had it set to appear by default, but I figured I'd better get a sanity check here first. The code is brought in by a very short initialisation script only on that particular page to save a bit of code bloat.
We're hoping to soft-launch the Teahouse project on Monday Pacific (I've been wrapped up in training and slow on getting this done). Please let me know before then if there's any problem in putting this in a gadget, or if I need to be doing it some other way.
Thanks a lot. — Andrew Garrett • talk 23:18, 24 February 2012 (UTC)
- A few people took a look at the code, and there weren't any objections, so I went ahead and did this. — Andrew Garrett • talk 02:25, 28 February 2012 (UTC)
- What does it do? Rich Farmbrough, 23:13, 13 September 2012 (UTC).
Have ProveIt use ResourceLoader?
Does anyone see any issue if I enable ResourceLoader for ProveIt? Initially, this would just be so MediaWiki:Gadget-ProveIt.js can be unminiifed, but ResourceLoader minifies it when serving. I do have a dependency on jQuery Tabs, but I'd like to keep using mw.loader.using so it also works in dev (when I'm testing in non-gadget mode). Superm401 - Talk 05:09, 4 March 2012 (UTC)
Done I went ahead and did this, adding the dependency on tabs (as well as highlight). I did keep in the using. If you notice any issues, please post on User talk:ProveIt GT. Superm401 - Talk 07:22, 7 December 2012 (UTC)
NewDiff gadget updated
The NewDiff gadget has been updated and is now based on r133098, designed by Trevor Parscal, which is currently in trunk, with some minor adjustments. Comments welcome. — Edokter (talk) — 12:35, 10 March 2012 (UTC)
Question
Is there any way to disable a Gadget for only one user. I ask because this user is effectively banned from using HotCat, and I think he is violating this by bypassing the automatic saving of HotCat and modifying the edit summary. (I only know about it, because he forget to make this two times.) Armbrust, B.Ed. Let's talkabout my edits? 19:02, 17 March 2012 (UTC)
edit summary gadget
- Is there a way to add personalized edit summaries to the default edit summaries in the drop down menu of the edit summary gadget?
- can we change the existing edit summaries ? -- ÐℬigXЯaɣ 21:11, 17 March 2012 (UTC)
My sandbox gadget misdirects to incubator wiki when accessed via https
When I'm accessing en.wiki via https (secure.wikimedia.org) and click on the "My sandbox" link - it takes me to https://secure.wikimedia.org/wikipedia/incubator/wiki/W/index.php/Special:MyPage/sandbox - not quite sure how that can be fixed, but it probably should be. --Versageek 21:28, 19 March 2012 (UTC)
- Duplicate of thread raised three minutes earlier at MediaWiki talk:Gadget-mySandbox.js. Please see WP:MULTI. --Redrose64 (talk) 23:43, 19 March 2012 (UTC)
Gadget-dropdown-menus — watch/unwatch problem
A few months ago, the "watch page" / "unwatch page" function in Gadget-dropdown-menus.js started sending me to an annoying new page asking me to click on a "Yes" button to confirm my request to watch or unwatch a page. The default "watch" / "unwatch" button (displayed when the gadget is not being used) doesn't do this.
I did some poking around and believe the reason for this change in behaviour is that a new "token" parameter was added to the MediaWiki watch/unwatch API (see here). The default watch/unwatch button action includes this token parameter, but the watch/unwatch menu item in the dropdown-menus gadget does not. — Richwales 03:06, 25 June 2012 (UTC)
Teahouse Response gadget
Moved to Wikipedia:Gadget/proposals#Teahouse Response gadget. Equazcion (talk) 20:26, 10 Aug 2012 (UTC)
Deprecate textareasansserif?
I just noticed that for a long time now, MediaWiki has had a preference for "Edit area font style:" in the Editing tab, which includes an option for sans-serif, effectively making this gadget obsolete. I propose we immediately edit MediaWiki:Gadget-textareasansserif to state that this gadget is obsolete. To entirely remove the gadget, we have a few options:
- If the Foundation privacy policies permit generation of such a list, set a deadline for removal and notify all users using the gadget of the new preference.
- Adjust the gadget to display a notice informing users of the new preference, and set a deadline for removal.
- Just announce it somewhere (WP:VP? Watchlist notice?) with a deadline.
Thoughts? Anomie⚔ 03:23, 3 September 2012 (UTC)
- Personally, I'd go for #2 or #3, in that order. The code to display the message to users of the gadget would be something as simple as
mediaWiki.util.jsMessage('<p>You are currently using the "Make text fields use a sans-serif font" gadget. <b>This gadget will be turned off on $DATE!</b></p><p>For some time now, MediaWiki has included a preference to select the text area font in the <a href="//wiki.riteme.site/wiki/Special:Preferences#mw-prefsection-editing" target="preferences">Editing tab</a>; to keep your sans-serif font, please activate this preference. To stop receiving this message, please turn off this gadget in your preferences.</p>','textareasansserif-deprecated');
- added to MediaWiki:Gadget-textareasansserif.js (and the MediaWiki:Gadgets-definition adjusted to load this,
textareasansserif[ResourceLoader|dependencies=mediawiki.util]|textareasansserif.css|textareasansserif.js). Anomie⚔ 03:23, 3 September 2012 (UTC)
- I have no clue what all that JS means, but I would be happy to remove both this gadget and the one below it. We have too many gadgets (which makes it hard to see the preferences page), so getting rid of (almost) useless ones is good. David1217 What I've done 22:24, 12 September 2012 (UTC)
- I support the proposed removal. Hazard-SJ ✈ 01:43, 13 September 2012 (UTC)
- Support removal Makes sense. • Jesse V.(talk) 15:39, 15 September 2012 (UTC)
- Yup. 1 would breach privacy, but 2 and 3 should be more than enough. -— Isarra ༆ 18:07, 16 September 2012 (UTC)
Support removal. There's no good reason for opposing the change now that the preference doesn't apply to just #wpTextbox1, and we can even automatically change users' preferences for them. PleaseStand (talk) 03:12, 27 September 2012 (UTC)
Put this in a page MediaWiki:Gadget-textareasansserif.js:
new mediaWiki.Api().post( {action: 'options', token: mediaWiki.user.tokens.get( 'editToken' ), change: 'editfont=sans-serif|gadget-textareasansserif'} );
Change the relevant line in MediaWiki:Gadgets-definition to:
textareasansserif[ResourceLoader|dependencies=mediawiki.api,mediawiki.user]|textareasansserif.js|textareasansserif.css
And update MediaWiki:Gadget-textareasansserif to:
To use a sans-serif font for editing pages, change the "Edit area font style" in the [[#mw-prefsection-editing|"Editing" section]].
- That is an even better idea. But it's technically not the right token, even though currently the tokens are the same. I've adjusted the code and implemented it. Anomie⚔ 14:22, 29 September 2012 (UTC)
Transition script broken
I think a recent security patch to MediaWiki core broke the API's ability to disable the gadget. Moreover, the number of accounts with the gadget enabled rose from 5187 (on November 22) to 5203 (on November 29). Leaving the broken script enabled can only cause an increasing amount of unnecessary server load and potential user confusion. As two months have passed, all active users should have been switched over. Is it time to remove the gadget now? PleaseStand (talk) 21:49, 2 December 2012 (UTC)
- The bug is filed as T44639, I'll ask around tomorrow if it's urgent enough to be backported into 1.21wmf5 or if it has to wait for wmf6. As for the pref usage, that seems odd that it went up instead of down. Anomie⚔ 04:07, 3 December 2012 (UTC)
Does Gadget-NewDiff actually do anything anymore?
Now that the new diff colors have been in MediaWiki for some time now, does this gadget actually do anything useful? Or does it just set the diff colors to what they already are? Anomie⚔ 03:29, 3 September 2012 (UTC)
- It is basically obsolete, but... it does contain some adjustments to the site CSS (for which I have a bug open). — Edokter (talk) — 18:54, 12 September 2012 (UTC)
- If those fixes are good, shouldn't they just be applied instead of being in a gadget many won't bother with? Anomie⚔ 01:01, 13 September 2012 (UTC)
- I agree. "Gadgets" should only contain the most-used scripts. Hazard-SJ ✈ 01:38, 13 September 2012 (UTC)
- They're waiting for me to submit a changeset, but I haven't set up Git on my PC yet. — Edokter (talk) — 20:07, 14 September 2012 (UTC)
- If those fixes are good, shouldn't they just be applied instead of being in a gadget many won't bother with? Anomie⚔ 01:01, 13 September 2012 (UTC)
The change is part of 1.21wmf4. Is there any reason to keep this gadget now? PleaseStand (talk) 05:23, 27 November 2012 (UTC)
- You probably mean this one, which was merged November 10. I don't know if it has been deployed yet. — Edokter (talk) — 22:19, 27 November 2012 (UTC)
- It appears it has been deployed. — Edokter (talk) — 22:24, 27 November 2012 (UTC)
HotInterwiki
As you are aware that I am doing lots of my efforts on Urdu Wiki. I often work on Wikipedia to update Interwiki links and Categories link between the two Wikipedias i.e. Urdu & English Wikipedia. I am using "Hot Interwiki" link in Urdu wiki (find here) but couldn't succeed to find this link in English Wiki. Can you help me out to get this tool in English Wiki too so that I may enter Urdu interwiki link into English as I am usually make new categories on Urdu Wiki to categorize all article in a proper way. I only use English Wiki to enter Urdu interwiki and for this I've to spend lot of time to push the edit button on every single article on English Wiki to enter Urdu interwiki link.
I hope you will help me to get access to "Hot Interwiki" tool on English Wikipedia. Thanks --ساجد امجد ساجد (talk) 21:21, 28 October 2012 (UTC)
- A very similar thread already exists at Wikipedia:Gadget/proposals#HotInterwiki. --Redrose64 (talk) 22:05, 28 October 2012 (UTC)
Preference Help
I want helper about preference more specifically an editcount helper. Whom should I go? --Pratyya (Hello!) 15:06, 14 January 2013 (UTC)
- Try going to WP:VPT for programming help. Gary King (talk · scripts) 17:59, 14 January 2013 (UTC)
Gadgets must be explained
Can we please add a requirement that each new gadget must be explained clearly in the preference option itself and must be linked to a detailed explanation and/or illustration of its functionality? (I would have said "should" on the second part, but almost every gadget does something that would not be easy to explain to a newbie WP user, so it really should be "must". How can a user decide whether they want to use a gadget [or not use it, if it's enabled by default] if they can't even understand what it does?) Most gadgets do satisfy both requirements already, but new ones continue to be added that don't satisfy either. If this idea is rejected as instruction creep, then can the people who are actively involved in this and other relevant pages just please "police" the addition of new preferences more carefully? Today I went to My Preferences after not checking them in a long time, and I found several new gadgets, one of which was checked by default but not described sufficiently well for even an experienced WP user like me to figure out what the heck it did (took 10 minutes of searching). This shouldn't be allowed to happen. - dcljr (talk) 14:07, 16 February 2013 (UTC)
"Edit" section inks besides section titles
Up to yesterday they were right-aligned. I seem to recall it was a Gadget doing that. Can't find it. Was a Gadget removed recently? :) ·Salvidrim!· ✉ 01:09, 7 May 2013 (UTC)
- Yes, it was removed. The software was updated to show the edit link on the left by default. — Edokter (talk) — 01:13, 7 May 2013 (UTC)
- Mk. If I preferred it right-aligned like I had it, any plans for a gadget? ;) :) ·Salvidrim!· ✉ 01:16, 7 May 2013 (UTC)
- It could be done as a gadget, but I didn't think it was necessary since all you need is one line adding to either Special:Mypage/common.css or Special:Mypage/skin.css See also WP:VPT/Section edit links are migrating westwards, WP:VPT#.5Bedit.5D moved etc. --Redrose64 (talk) 09:30, 7 May 2013 (UTC)
span.mw-editsection { float:right; }
- It could be done as a gadget, but I didn't think it was necessary since all you need is one line adding to either Special:Mypage/common.css or Special:Mypage/skin.css
- Mk. If I preferred it right-aligned like I had it, any plans for a gadget? ;) :) ·Salvidrim!· ✉ 01:16, 7 May 2013 (UTC)
Notification gadget causing JS error for anonymous users
@Edokter: The Notifications gadget is causing a JS error for logged out users. The reason is that it loads ext.echo.overlay.js, which wasn't designed to function for anonymous users. I can fix this in ext.echo.overlay.js, but won't be able to deploy the fix until next week. Kaldari (talk) 19:47, 8 May 2013 (UTC)
- This may cause any default gadgets loaded after the Notifications gadget to fail for anonymous users as well (since ResourcesLoader bundles them into one JS file). Kaldari (talk) 19:54, 8 May 2013 (UTC)
- I tweaked the gadget to only enable it for logged in users (anyone with the "purge" user right) as logged out users should still see the OBOD. Thehelpfulone 20:06, 8 May 2013 (UTC)
- Changed to "minoredit". I think IPs can purge. — Edokter (talk) — 20:13, 8 May 2013 (UTC)
- I tweaked the gadget to only enable it for logged in users (anyone with the "purge" user right) as logged out users should still see the OBOD. Thehelpfulone 20:06, 8 May 2013 (UTC)
RfC: Are the Category:Wikipedians and its subcategories appropriate for Wikipedia
There is an ongoing RfC going on at Category talk:Wikipedians#RfC: Is this category and current subcategories appropriate for Wikipedia that gadget creators and users may be interested it. Technical 13 (talk) 12:19, 29 August 2013 (UTC)
Time of edit is missing in user contributions list when using Wildcard/IP-Range in german section of the Wikipedia
As known user contributions from an IP or a user can be listed. But additionally it is possible to list an IP-Range (activate CIDR-Settings). When listing a single IP or user, all the list entries have time of edit; but when listing an IP range, time of each edit is missing when expanding the entries. I was told that the script has to be adapted. Could please anyone help in adatping that script so that also time of edit will be listed? Please have a look to the german WP where I was describing the problem. I was told that this script (in the german WP) is affected and has to be adapted. Please have a look at this description of the problem; be aware that it is written in german language. Thank you. --ProloSozz (talk) 10:14, 10 January 2014 (UTC)
Clarify
"Collections of scripts should be applied as own entities."
What is an "own entity" when it is at home? (Looks like some kind of Google-translate from German.) All the best: Rich Farmbrough, 14:13, 7 November 2014 (UTC).
- @Rich Farmbrough: This diff seems to indicate that it means multiple scripts shouldn't be bundled into the same gadget unnecessarily. Jackmcbarn (talk) 17:16, 25 November 2014 (UTC)
- @Jackmcbarn: Thanks, kinda what I thought, but I was wary that "own entity" might be "eigen-foo" and have a technical meaning. I have changed the itm to read "# Collections of scripts should be split if they have disparate functions." which I hope is clearer. If not feel free to improve, as always. All the best: Rich Farmbrough, 17:47, 25 November 2014 (UTC).
- @Jackmcbarn: Thanks, kinda what I thought, but I was wary that "own entity" might be "eigen-foo" and have a technical meaning. I have changed the itm to read "# Collections of scripts should be split if they have disparate functions." which I hope is clearer. If not feel free to improve, as always. All the best: Rich Farmbrough, 17:47, 25 November 2014 (UTC).
Switcher gadget
UTC clock gadget no longer displayed
At some point a few weeks ago, the UTC clock stopped appearing in the personal toolbar. I don't recall making any changes that might have interfered with it. I've tried turning it off and on but it doesn't help. I welcome suggestions for other things I could try to fix it. Jojalozzo 15:11, 5 January 2015 (UTC)
- Works for me. There are a lot of scripts loaded from your vector.js; one of them might be broken, blocking all other JavaScript/gadgets. Disable them all and re-enable them one by one.
-- [[User:Edokter]] {{talk}}15:51, 5 January 2015 (UTC)- Thank you for the suggestion. I may try that but the last change to my vector.js was March 2013 so I don't expect that is where the problem is. Jojalozzo 05:09, 6 January 2015 (UTC)
- The last change to YOURS, yes, but what about all of those scripts you are dynamically importing? — xaosflux Talk 20:42, 16 January 2016 (UTC)
- Thank you for the suggestion. I may try that but the last change to my vector.js was March 2013 so I don't expect that is where the problem is. Jojalozzo 05:09, 6 January 2015 (UTC)
Proposal to add global JavaScript
There is an ongoing discussion that watchers of this page may be interested in on Proposal to add global JavaScript and add an extra step for new users to get live IRC help. — {{U|Technical 13}} (e • t • c) 19:40, 28 April 2015 (UTC)
- This discussion was archived at Wikipedia:Village pump (proposals)/Archive 123#RfC: Proposal to add global JavaScript and redirect all IRC help links through a disclaimer page. —andrybak (talk) 11:22, 13 July 2024 (UTC)
Missing Twinkle
Why is Twinkle missing from the Gadgets menu? Coconuts31 (talk) 13:17, 2 July 2015 (UTC)
- @Coconuts31: I still see it, under the "Browsing" header. Conifer (talk) 23:20, 2 July 2015 (UTC)
- I still don't. Coconuts31 (talk) 14:42, 5 July 2015 (UTC)
- @Coconuts31: It's only shown for WP:AUTOCONFIRMED users. You've made sufficient edits, but not enough time has yet elapsed. You should become autoconfirmed four days after registration, i.e. on 5 July 2015 at 21:56 (UTC), which is in five and a half hours' time. --Redrose64 (talk) 16:24, 5 July 2015 (UTC)
- I still don't. Coconuts31 (talk) 14:42, 5 July 2015 (UTC)
WatchlistGreenIndicators
I'm checking the descriptions of various gadgets to make sure they match what the gadget does and I've come across MediaWiki:Gadget-WatchlistGreenIndicators.css. Its description at MediaWiki:Gadget-WatchlistGreenIndicators says
- Display green collapsible arrows and green bullets for changed pages in your Watchlist, History and Recent changes
but as far as I can tell, this gadget displays only green bullets and only for the watchlist. I see no collapsible green arrows and I see no effect on the History and Recent changes pages. (Note: this gadget requires you to bypass your browser's cache each time you toggle its preference for the setting to come into effect.) Can somebody confirm or deny that they see same behavior. The description may be out-of-date. Courtesy ping: Edokter. Jason Quinn (talk) 15:56, 5 July 2015 (UTC)
- @Jason Quinn: As you noticed, this was recently upgraded by Edokter (talk · contribs) and there is discussion at Wikipedia:Village pump (technical)/Archive 137#Changed pages on my watchlist, Wikipedia:Village pump (technical)/Archive 137#Watchlist design change feedback, Wikipedia:Village pump (technical)/Archive 137#Hiding the dot and Wikipedia:Village pump (technical)/Archive 138#Watchlist announcements leaving a gap. Probably elsewhere too. --Redrose64 (talk) 16:29, 5 July 2015 (UTC)
- Jason Quinn, on my end, I don't need to clear my cache. The arrows mentioned are visible in the enhanced watchlist only, which you get by enabling both Group changes by page in recent changes and watchlist and Expand watchlist to show all changes, not just the most recent in your preferences.
-- [[User:Edokter]] {{talk}}16:34, 5 July 2015 (UTC)
PurgeTab gadget
Useful for me. - Vargskelethor (talk) (sandbox) (userboxes) 19:38, 10 August 2016 (UTC)
libLua and libSensitiveIPs
I've proposed adding two new gadgets, libLua and libSensitiveIPs, over at WP:VPT#Sensitive IP addresses follow-up. If people want to review the code and/or make comments, I'd be most grateful. — Mr. Stradivarius ♪ talk ♪ 14:00, 22 September 2016 (UTC)
- For the record, the discussion was archived at Wikipedia:Village pump (technical)/Archive 149#Sensitive IP addresses follow-up. —andrybak (talk) 11:26, 13 July 2024 (UTC)
Watchlist bolding
The bolding of unread articles on my watchlist has for some reason turned itself on recently, despite not being selected in my preferences. I tried selecting it, saving, then unselecting, but I can't seem to make it go away. Any advice? Cheers, Number 57 18:57, 10 October 2016 (UTC)
- @Number 57: Please see Wikipedia:Village pump (technical)#Gadget CSS order. --Redrose64 (talk) 18:10, 11 October 2016 (UTC)
- The discussion was archived to Wikipedia:Village pump (technical)/Archive 150#Gadget CSS order. —andrybak (talk) 11:27, 13 July 2024 (UTC)
Question
Why is MediaWiki:Gadget-WatchlistBase.css loaded as a gadget? Shouldn't it be loaded via the MediaWiki:Common.css or something similar since the line in preferences says "This loads the base style for the watchlist. Please do not disable this option."? --TerraCodes (talk to me) 03:44, 26 October 2016 (UTC)
- @TerraCodes: MediaWiki:Common.css is loaded for all users, even those who are logged out, so it is a good idea to keep it as small as possible. Logged-out users don't have watchlists, so it makes sense to load the watchlist CSS only for logged-in users. This can't be done via Common.css, but it can be done using gadgets, so that's why it is the way it is. I think it should be possible to hide the entry for it in preferences, though, if it isn't already. — Mr. Stradivarius ♪ talk ♪ 03:53, 26 October 2016 (UTC)
gadget-watchlist-notice
 | This edit request to MediaWiki:gadget-watchlist-notice has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
This is an edit request for MediaWiki:Gadget-watchlist-notice, the descriptor for the gadget that enables watchlist notices. The gadget does more than what the description says; as it is, the current text is misleading in that folks may think the notices would not be dismissable. Please change the text to: Display [[Wikipedia:Watchlist notices|watchlist notices]] (see also the similar similar to MediaWiki:Gadget-geonotice. Thanks! — Andy W. (talk) 23:29, 16 November 2016 (UTC)
Done — Martin (MSGJ · talk) 12:17, 17 November 2016 (UTC)
- Andy M. Wang, MSGJ: I just got very confused because of this change. If the gadget is disabled:
- are the notices always hidden? In this case, MediaWiki:Gadget-watchlist-notice-core.js code comment should be updated as well.
- or are they not dismissable? In this case, the description change is incorrect.
- Od1n (talk) 13:44, 9 April 2017 (UTC)
- If the gadget is deactived, the notices are completely hidden. However, if JavaScript is deactivated, the notices are shown (and of course not dismissable). Od1n (talk) 07:11, 11 April 2017 (UTC)
- Andy M. Wang, MSGJ: I just got very confused because of this change. If the gadget is disabled:
@Andy M. Wang: please could you attend to the queries raised above? — Martin (MSGJ · talk) 07:30, 20 April 2017 (UTC)
- @Od1n: Andy doesn't seem to be actively editing at the moment. Would you like me to revert the change above? — Martin (MSGJ · talk) 07:31, 20 April 2017 (UTC)
- Considering the regular usage is with JavaScript enabled, the gadget definition is fine. However, the comment in MediaWiki:Gadget-watchlist-notice-core.js could be improved. Would you please apply this change? Od1n (talk) 20:49, 20 April 2017 (UTC)
- @Od1n and MSGJ: Sorry I'm late to this... my 2 cents: I don't think there's anything in the code or doc that really needs to be changed since the general case is that JavaScript is enabled (and we're pretty much assuming that on this site I think). If it's just about adding that comment a.k.a this change, sounds okay. (I don't have power to make any changes.) — Andy W. (talk) 04:26, 7 May 2017 (UTC)
- Considering the regular usage is with JavaScript enabled, the gadget definition is fine. However, the comment in MediaWiki:Gadget-watchlist-notice-core.js could be improved. Would you please apply this change? Od1n (talk) 20:49, 20 April 2017 (UTC)
- I have adjusted the comment on MediaWiki:Gadget-watchlist-notice-core.js — Martin (MSGJ · talk) 11:35, 22 May 2017 (UTC)
Edit summary gadget was working now not working
Edit summary gadget was working now not working.
The drop down menu options are still there, just when I click on them they don't show up in the edit summary box.
Any idea on how to fix it? Sagecandor (talk) 22:21, 1 December 2016 (UTC)
- @Sagecandor: It's Thursday, the normal day for MediaWiki software deployment. My guess is a breaking change with the latest update, possibly related to the planned removal of the legacy "wikibits" JavaScript module, see Wikipedia:Village pump (technical)/Archive 145#Breaking change: wikibits. --Redrose64 (talk) 00:07, 2 December 2016 (UTC)
- @Redrose64:Oh okay that makes sense, thank you for the helpful explanation! Sagecandor (talk) 00:15, 2 December 2016 (UTC)
- I left a note at Wikipedia:Village pump (technical)#Several technical problems where others have commented. --Redrose64 (talk) 09:35, 2 December 2016 (UTC)
- This was archived at Wikipedia:Village pump (technical)/Archive 151#Several technical problems. —andrybak (talk) 11:29, 13 July 2024 (UTC)
- I left a note at Wikipedia:Village pump (technical)#Several technical problems where others have commented. --Redrose64 (talk) 09:35, 2 December 2016 (UTC)
- @Redrose64:Oh okay that makes sense, thank you for the helpful explanation! Sagecandor (talk) 00:15, 2 December 2016 (UTC)
"Place the category box above all other content"
How can I find who maintains the "Place the category box above all other content" gadget listed in the Preferences panel? czar 05:25, 8 September 2017 (UTC)
- @Czar: Ordinarily I'd say:
- go to Special:Gadgets
- search for the description of the gadget concerned
- on the next line (the one beginning "Uses:") try each link in turn
- for each of these, use the "View history" tab to see who the main contributors are.
- In this case however, the code is Gadget-CategoryAboveAll.js which was written by Docu (talk · contribs) - who is no longer around. If there is a problem, I suggest that you drop a note at WP:VPT. --Redrose64 🌹 (talk) 20:42, 8 September 2017 (UTC)
- I guess this code is ab it better. → User: Perhelion 00:00, 22 February 2019 (UTC)
Proposal for a new gadget (talk-tab-count)
Just in case anyone watches this page and not WP:VPT, I've opened a proposal over there to make User:Enterprisey/talk-tab-count into a gadget: WP:VPT#Proposal to make talk-tab-count a gadget Enterprisey (talk!) 05:56, 9 January 2018 (UTC)
- VPT discussion is archived at Wikipedia:Village pump (technical)/Archive 161#Proposal to make talk-tab-count a gadget. —andrybak (talk) 11:52, 13 July 2024 (UTC)
search-new-tab isn't needed any more, due to being default browser behaviour?
The search-new-tab gadget says it lets you ctrl-click on a link in the search results box to open it in a new tab. As far as I can tell, this is actually default browser behaviour nowadays, as even without this gadget a ctrl-click opened a search link in a new tab in Chrome, Firefox, and Internet Explorer for me. Given that the gadget appears to serve no purpose, I think it'd be best to remove it to remove clutter. --Deskana (talk) 14:38, 7 July 2018 (UTC)
- I've removed the gadget. --Deskana (talk) 23:18, 10 July 2018 (UTC)
- Ctrl+click doesn’t work for me in Firefox (61.0.1, Win7) on any form button (i.e.
<submit>,<button>etc.). Ctrl+click on search suggestions works, as these are implemented with HTML<a>tags. (I haven’t used the gadget, though, as I don’t often need this functionality, just wanted to let you know about this.) —Tacsipacsi (talk) 00:11, 11 July 2018 (UTC)- I don't think Ctrl-click has ever worked on buttons in FF. I can confirm Tacsipacsi's suspicion that disabling this gadget has removed functionality for users, at least in FF. The gadget is required to open search results in a new tab. - dcljr (talk) 05:46, 11 July 2018 (UTC)
- What version/operating system? Firefox 61 on Win 10 provides for ctrl+click to new tab. --Izno (talk) 13:56, 11 July 2018 (UTC)
- I noted my primary system configuration above, but this doesn’t work for me on Windows 10 either (Win10 April 2018 Update with June security updates, Firefox 61.0.1). Maybe you’re using a browser extension to achieve this (see about:addons)? Or you mean regular links like this? These work for everyone, the problem is with buttons like . —Tacsipacsi (talk) 14:50, 11 July 2018 (UTC)
- What version/operating system? Firefox 61 on Win 10 provides for ctrl+click to new tab. --Izno (talk) 13:56, 11 July 2018 (UTC)
- I don't think Ctrl-click has ever worked on buttons in FF. I can confirm Tacsipacsi's suspicion that disabling this gadget has removed functionality for users, at least in FF. The gadget is required to open search results in a new tab. - dcljr (talk) 05:46, 11 July 2018 (UTC)
I'm confused. The gadget was described as "Open search results in a new tab or window when holding down the Ctrl key", but the complaints here are about ctrl-clicking on buttons, which is unrelated to what the gadget said it was doing. For example, the example immediately above this comment is a button, not a search result. Am I misunderstanding? --Deskana (talk) 15:12, 11 July 2018 (UTC)
- Search on this wiki is implemented either through the search box at the top right of every page (in the Vector skin), where there is a magnifying glass button/icon to perform the search, or through Special:Search where there is a "Search" button to do the same. For me, both methods fail to open a new tab with Ctrl-click or with Ctrl-Enter on FF 52.6.0 for Gentoo Linux and on IE 11.0.9600.19035 for Windows 7. However, Ctrl-click in both places does work for me on Chrome 67.0.3396.99 for WIndows 7. I can only confirm Ctrl-Enter used to work on FF 52.6.0 (and at least a couple of previous versions — not sure which ones) on Gentoo Linux when the gadget was enabled. Do we know of any other Wikimedia wikis where this gadget is still enabled? I don't know of any, but if so that would enable further testing of the gadget itself. (Or you could just re-enable the gadget here, which is what I'd like you to do.) - dcljr (talk) 15:33, 11 July 2018 (UTC) [Edits to this comment after first reply: added "/icon", 15:38, 11 July 2018 (UTC); added "(in the Vector skin)". - dcljr (talk) 17:29, 11 July 2018 (UTC)]
- The following elements were manipulated by this gadget:
#searchform, #searchbox, #search, .search-types, #search-types, #powersearch—TheDJ (talk • contribs) 15:35, 11 July 2018 (UTC)- Please note (primarily talking to Deskana here) that the gadget isn't about links at all (whether in search results or not), for which Ctrl-click always works on "all" modern browsers, AFAIK. It is about getting to the search results in the first place. - dcljr (talk) 15:40, 11 July 2018 (UTC)
- So, it seems the gadget description was at best wrong, or at worst very misleading. So, I'm still fairly confused about what exactly the problem is. The issue is that with the gadget enabled when you clicked on the magnifying glass in the search bar then it would open in a new tab, but now with no gadget it doesn't? This seems like very niche functionality, and having niche functionality a bad pattern. That said, you can always still enable the gadget directly by putting
importScript('MediaWiki:Gadget-search-new-tab.js')in your common.js. --Deskana (talk) 05:46, 12 July 2018 (UTC)- Actually, the description you quoted above says exactly what the gadget does. You just misunderstood and thought it had something to do with links. And like I said, I used Ctrl-Enter, actually, instead of Ctrl-click, but the results are (were) the same. Look, I'm not trying to be rude here, but you really shouldn't be disabling gadgets without understanding what they do in the first place. Did you look at the code? Did you ask the author of the gadget or (if different) the user who originally enabled it what it did? Did you test the gadget yourself, in the same manner you suggested I could use? Do you know how many users had the gadget enabled? I suspect the answer to all of these (based on what you have said here) is "no", in which case you are blindly trying out a blunt-force "solution" to a likely nonexistent "problem", thereby creating a problem (inconvenience, anyway) in the process. Sorry if this seems harsh. Things like this just piss me off (people doing something they shouldn't be doing and then refusing to undo it for no good reason). - dcljr (talk) 10:46, 12 July 2018 (UTC)
- Whoa boy, that's a lot of assumptions. Let's go through them. Did I look at the code? Yes, but I clearly didn't understand it correctly based on what happened here. Did I ask the author? No. Did I test it myself? Yes, I enabled it through the gadget interface before I disabled it, and it worked the same for me both with and without the gadget enabled. Did I check how many users were using it? Yes, there are just over 7,000 users of the gadget. Anyway, I've undone my change, and you can rest assured that I won't work on gadgets again. --Deskana (talk) 19:01, 12 July 2018 (UTC)
- Using common.js is by far the worst practice to enable anything. Yesterday people were told to use
document.write()with HTTP links. It doesn’t work today, but 11,500 people still use it (including you). Today you suggest usingimportScript(), which will be gone by tomorrow (actually it’s planned to be deprecated in the near future). Tomorrow someone else will suggest another method, which may also be gone at some point. So people have custom JSs which are only useful to create security problems like using non-secure URLs. Maybe the description can be improved (although it seems that you’re the only one who didn’t understand it), but disabling a gadget on your own without understanding its functions is simply unacceptable. English Wikipedia is certainly not the place that lacks admins familiar with JavaScript, so let them manage gadgets. —Tacsipacsi (talk) 14:33, 12 July 2018 (UTC)- Tacsipacsi, Huh? Each user has their own common.js file which applies in each skin (yours is User:Tacsipacsi/common.js. You are confusing that with MediaWiki:common.js. --Izno (talk) 17:09, 12 July 2018 (UTC)
- Why would I confuse it? I know that the user JavaScript is not the same as the site-wide one. I was only speaking about the former; the site-wide Common.js doesn’t contain any
document.write()orimportScript(). The user JavaScript can also have security problems; of course not for everybody, only for its owner, but for them it can. —Tacsipacsi (talk) 21:46, 12 July 2018 (UTC)
- Why would I confuse it? I know that the user JavaScript is not the same as the site-wide one. I was only speaking about the former; the site-wide Common.js doesn’t contain any
- Sorry for giving incorrect advice about using
importScript(). Sorry for apparently being the only person to misunderstand the gadget description. Sorry for not having good enough knowledge of JavaScript for you. I've undone my change, and you can rest assured that I won't work on gadgets again. Hopefully that resolves your concerns. --Deskana (talk) 19:01, 12 July 2018 (UTC)- Thank you. —Tacsipacsi (talk) 21:46, 12 July 2018 (UTC)
- @Deskana: It wasn't my intention to have you never "work on gadgets again", just to be (much) more careful about disabling things. BTW (to no one in particular), I find that I had to re-enable the gadget in my preferences, since it "came back" unchecked. This seems a little weird to me. I would have hoped that a more specific action would be required to make MediaWiki "forget" users' preferences than simply removing entries at MediaWiki:Gadgets-definition (like maybe a sysadmin running a script). I guess not! - dcljr (talk) 08:42, 13 July 2018 (UTC)
- Same with flipping the default bit, that also wipes everyones setting. —TheDJ (talk • contribs) 08:47, 13 July 2018 (UTC)
- @Dcljr: Don't worry about it. Working to improve the gadgets space seems like it'll be an uphill battle, and I deal with enough of those as a Wikimedian without adding more, so I've lost interest. It's not a big deal. I've got plenty of other things to do instead. --Deskana (talk) 10:35, 13 July 2018 (UTC)
- @Deskana: It wasn't my intention to have you never "work on gadgets again", just to be (much) more careful about disabling things. BTW (to no one in particular), I find that I had to re-enable the gadget in my preferences, since it "came back" unchecked. This seems a little weird to me. I would have hoped that a more specific action would be required to make MediaWiki "forget" users' preferences than simply removing entries at MediaWiki:Gadgets-definition (like maybe a sysadmin running a script). I guess not! - dcljr (talk) 08:42, 13 July 2018 (UTC)
- Thank you. —Tacsipacsi (talk) 21:46, 12 July 2018 (UTC)
- BTW, on the matter of improving the description, might it help to say, "Open page of search results in a new tab or window when holding down the Ctrl key" (added text noted)? And I guess "or window" is stated just because some browsers provide their own option to change the Ctrl key behavior to open a window instead of a tab, in which case perhaps that phrase should be in parentheses? Thus: "Open page of search results in a new tab (or window) when holding down the Ctrl key". - dcljr (talk) 08:56, 13 July 2018 (UTC)
- Another BTW: I'm not sure User:Timeshifter, the gadget author, needs to be consulted now, but he is still active. So if he'd like to weigh in on anything in this discussion… - dcljr (talk) 09:14, 13 July 2018 (UTC)
- Tacsipacsi, Huh? Each user has their own common.js file which applies in each skin (yours is User:Tacsipacsi/common.js. You are confusing that with MediaWiki:common.js. --Izno (talk) 17:09, 12 July 2018 (UTC)
- Actually, the description you quoted above says exactly what the gadget does. You just misunderstood and thought it had something to do with links. And like I said, I used Ctrl-Enter, actually, instead of Ctrl-click, but the results are (were) the same. Look, I'm not trying to be rude here, but you really shouldn't be disabling gadgets without understanding what they do in the first place. Did you look at the code? Did you ask the author of the gadget or (if different) the user who originally enabled it what it did? Did you test the gadget yourself, in the same manner you suggested I could use? Do you know how many users had the gadget enabled? I suspect the answer to all of these (based on what you have said here) is "no", in which case you are blindly trying out a blunt-force "solution" to a likely nonexistent "problem", thereby creating a problem (inconvenience, anyway) in the process. Sorry if this seems harsh. Things like this just piss me off (people doing something they shouldn't be doing and then refusing to undo it for no good reason). - dcljr (talk) 10:46, 12 July 2018 (UTC)
- So, it seems the gadget description was at best wrong, or at worst very misleading. So, I'm still fairly confused about what exactly the problem is. The issue is that with the gadget enabled when you clicked on the magnifying glass in the search bar then it would open in a new tab, but now with no gadget it doesn't? This seems like very niche functionality, and having niche functionality a bad pattern. That said, you can always still enable the gadget directly by putting
- Please note (primarily talking to Deskana here) that the gadget isn't about links at all (whether in search results or not), for which Ctrl-click always works on "all" modern browsers, AFAIK. It is about getting to the search results in the first place. - dcljr (talk) 15:40, 11 July 2018 (UTC)
- The following elements were manipulated by this gadget:
(unindent). I just tested with the gadget on and off. In Firefox 61.0.1 in Windows 7 Home Premium. Enabling the gadget helps when clicking the magnifying glass icon when doing a search from the top-right search form. Without the gadget ctrl-clicking that icon ends up with the search results list in the same tab.
Ctrl-clicking without the gadget works when clicking items in the dropdown list.
I will be back after testing at Special:Search.
By the way, I did not create this gadget. I vaguely remember passing it on, and encouraging it be made a gadget in order to make it a lot easier to use by more people. I am not a developer, and I may have hacked at it, but someone else originally made it. --Timeshifter (talk) 18:09, 13 July 2018 (UTC)
- Testing at Special:Search. The gadget helps more here. Enter a search term. Without the gadget ctrl-clicking does not help when clicking the "search" button. Also, ctrl-clicking items in the dropdown list does not open anything in a new tab.
- After enabling the gadget ctrl-clicking the "search" button opens results in a new tab. Ctrl-clicking items in the dropdown list also opens results in a new tab. --Timeshifter (talk) 18:30, 13 July 2018 (UTC)
- Maybe change the gadget description to something like this:
- "Always get search result list in a new tab or window when holding down the Ctrl key."
- --Timeshifter (talk) 18:38, 13 July 2018 (UTC)
Gadget links
Would it be possible to include a link either to the documentation of the gadget or to its Javascript page in the Gadget preferences page? I might also suggest including the name for each item as well. It would aid recognizability and findability for trying to get changes to gadgets made for our not-so-well-known-as-Twinkle gadgets in the list. --Izno (talk) 04:02, 24 October 2018 (UTC)
- I think this is a great idea! Maybe VPT/VPPR? This page isn't highly-watched. Enterprisey (talk!) 05:41, 24 October 2018 (UTC)
- I have no idea where but some page or another listed this one. @Enterprisey: As it happens, Special:Gadgets is linked on Special:Preferences, so that at least gets you to the Javascript page for the gadget. --Izno (talk) 14:09, 24 October 2018 (UTC)
- @Izno and Enterprisey: are you referring to this page: Special:Preferences#mw-prefsection-gadgets? You should already be able to do this, see for example the line:
Require confirmation before performing rollback on mobile devices- It has a link to the documentation as provided from MediaWiki:Gadget-confirmationRollback-mobile. Any of those can be updated and it should be uncontroversial. — xaosflux Talk 14:15, 24 October 2018 (UTC)
- The "work" on this is going to be finding all of the documentation pages and getting the edits made, feel free to tackle this and add edit requests to the definition pages. — xaosflux Talk 14:16, 24 October 2018 (UTC)
- Yes, I doubt it is controversial; I just don't know where to make the edit requests. --Izno (talk) 14:47, 24 October 2018 (UTC)
- @Izno: here is where to find them:
- Go to MediaWiki:Gadgets-definition
- On each line take the first block of text (e.g.
modrollback), store this in your head as$1 - Go to MediaWiki:Gadget-$1 (e.g. MediaWiki:Gadget-modrollback)
- That is what shows on the Special:Preferences#mw-prefsection-gadgets page, you can make an edit request on the talk page of any of those pages (e.g. MediaWiki talk:Gadget-modrollback)
- Does that help? — xaosflux Talk 15:12, 24 October 2018 (UTC)
- Yes, that should do. I'll go poke around. :) --Izno (talk) 15:56, 24 October 2018 (UTC)
- @Izno: here is where to find them:
- Yes, I doubt it is controversial; I just don't know where to make the edit requests. --Izno (talk) 14:47, 24 October 2018 (UTC)
- The "work" on this is going to be finding all of the documentation pages and getting the edits made, feel free to tackle this and add edit requests to the definition pages. — xaosflux Talk 14:16, 24 October 2018 (UTC)
Voluntary code review
Anyone interested in participating in a voluntary "request for code review" process? Please discuss at Wikipedia talk:User scripts#Voluntary code review (not here) - Evad37 [talk] 03:42, 20 February 2019 (UTC)
- This was implemented as Wikipedia:Code review. Discussion is archived at Wikipedia talk:User scripts/Archive 6#Voluntary code review. —andrybak (talk) 11:55, 13 July 2024 (UTC)
Proposed change to Mediawiki:Gadget-markblocked.js
Hi, all, I'd like to make a change to Mediawiki:Gadget-markblocked.js, and wanted to discuss it here first. You can see the diff of what I'd like to change here: Special:Diff/862434408/884449263. Currently, when you go to an indefblocked user's talk page history, all of the datestamped history links will be styled as a link to an indefblocked user. This causes the distinction between revdeled and non-revdeled edits to be lost (at least for admins), since it overwrites the normal strikethrough-italic styling of a revdeled link. My changes exclude the datestamp links from consideration, preserving the extra information about revdel that is otherwise lost. Screenshots of the effect included. Thoughts? Writ Keeper ⚇♔ 18:52, 21 February 2019 (UTC)
- +1 Since becoming an admin (as if you're a non-admin, the revdeleted revision links are also grayed out), I've often had to view the history logged out (there are legit uses for an incognito window!) to make any sense of the history, which I shouldn't need to do since I don't see any reason for every revision link of the history to be struck-through. Galobtter (pingó mió) 19:18, 21 February 2019 (UTC)
- This mess made me think the same thing today, thanks for taking action! Changes look good, although I think
return`ing on just.mw-changeslist-datewould be sufficient and looks clearer to me. Unless that mucks up sysops viewing history with suppressed revisions? ~ Amory (u • t • c) 01:58, 22 February 2019 (UTC)- Haha, nah, I just like having the
(cur|prev)links be without lines, too (also shown in the screenshots). It's not necessary at all; in the interest of being conservative with changes, I'll leave it out. Writ Keeper ⚇♔ 03:01, 22 February 2019 (UTC)- I'm not wild about it either, but in the case of editors editing a blocked user's talk page, they impart extra information that, yes, that user is blocked, regardless of whether the revision's editor is blocked. One thing to do might be to exclude some combination of
.comment,.mw-history-undo, and.mw-rollback-link. It starts to get a bit unwieldy, but crossing out rollback/undo might send the wrong message. The edit summaries are somewhere in-between IMO; crossed out emphasizes the page you're on is that of a blocked user (à la cur/prev) but could(?) also be misleading/overly difficult to read. ~ Amory (u • t • c) 10:53, 22 February 2019 (UTC)- Yeah, I was considering doing the rollback and undo buttons, too, but decided against it just because of how bloat-y the if statement was getting. It's definitely a good idea, though. Writ Keeper ⚇♔ 15:44, 22 February 2019 (UTC)
- I'm not wild about it either, but in the case of editors editing a blocked user's talk page, they impart extra information that, yes, that user is blocked, regardless of whether the revision's editor is blocked. One thing to do might be to exclude some combination of
- Haha, nah, I just like having the
- Sounds like a good idea. Thanks for writing the patch! Enterprisey (talk!) 05:08, 22 February 2019 (UTC)
Okay, I went ahead and did the thing. I did it for the history entries, rollback links, and undo links, but not the cur/prev links. LMK with any comments/questions/concerns, of course. Cheers, all! Writ Keeper ⚇♔ 17:16, 22 February 2019 (UTC)
- Gorgeous. ~ Amory (u • t • c) 01:58, 23 February 2019 (UTC)
Discussion at WP:VPT#XFDcloser gadget?
You are invited to join the discussion at WP:VPT#XFDcloser gadget?. - Evad37 [talk] 04:37, 27 October 2019 (UTC)
- The discussion is archived at Wikipedia:Village pump (technical)/Archive 177#XFDcloser gadget?. —andrybak (talk) 12:02, 13 July 2024 (UTC)
Gadget and userscript unit testing
I've created a script to make on-wiki unit testing a bit easier to implement. Please see WP:IANB § Gadget and userscript unit testing, and comment there (not here). - Evad37 [talk] 01:09, 11 December 2019 (UTC)
- The discussion is archived at Wikipedia:Interface administrators' noticeboard/Archive 1#Gadget and userscript unit testing. —andrybak (talk) 12:02, 13 July 2024 (UTC)
UTC time gadget
Hi - is there any way to make the UTC time toolbar display work for certain time zones, not just UTC? Would be a handy addition for Wikipedia. ɱ (talk) 00:54, 11 May 2020 (UTC)
- @Ɱ:, we don't maintain the UTC clock gadget here, you can ask for updates at mw:MediaWiki talk:Gadget-UTCLiveClock.js. — xaosflux Talk 02:09, 11 May 2020 (UTC)
- Thanks, there's no obvious link to it from the gadgets page. ɱ (talk) 02:26, 11 May 2020 (UTC)
- Added! — xaosflux Talk 02:49, 11 May 2020 (UTC)
- Thanks, there's no obvious link to it from the gadgets page. ɱ (talk) 02:26, 11 May 2020 (UTC)
- @Ɱ and Xaosflux: I've coded the update, but want to make sure its a good idea given the wide use; please see Wikipedia:Code review/UTCLiveClock DannyS712 (talk) 10:25, 11 May 2020 (UTC)
VPTECH thread on SHORTDESC gadget's metadata output
Please see Wikipedia:Village pump (technical)#Short description metadata issues. — SMcCandlish ☏ ¢ 😼 20:28, 19 May 2020 (UTC)
- The discussion is archived at Wikipedia:Village pump (technical)/Archive 181#Short description metadata issues. —andrybak (talk) 12:02, 13 July 2024 (UTC)
Delete Gadget and Gadget Definition namespaces
Please see Wikipedia:Village pump (proposals)#Delete Gadget and Gadget Definition namespaces. Alexcalamaro (talk) 05:34, 2 February 2021 (UTC)
- The discussion is archived at Wikipedia:Village pump (proposals)/Archive 176#Delete Gadget and Gadget Definition namespaces. —andrybak (talk) 12:02, 13 July 2024 (UTC)
Quick CSS formatting edit to MediaWiki:Gadget-NewImageThumb.js
| This edit request to MediaWiki:Gadget-NewImageThumb.js has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
The maintainer for this javascript is now retired. there are a number of suggestions on its discussion page suggesting similar things:
- remove the drop shadow
- remove the border
Could someone with .js editing privileges make the necessary edits? T.Shafee(Evo&Evo)talk 05:12, 3 March 2021 (UTC)
- Additionally, what do people think about replacing the entire caption background as white (similar to formatting at this page). T.Shafee(Evo&Evo)talk 05:16, 3 March 2021 (UTC)
Not done (as to the immediate edit request) this is a 'test' gadget so no big deal making tweaks to it; but they need to be written before they can be implemented. Once someone writes and tests changes, feel free to activate a new edit request at MediaWiki talk:Gadget-NewImageThumb. — xaosflux Talk 14:44, 3 March 2021 (UTC)
RegexMenuFramework
Does MediaWiki:Gadget-RegexMenuFramework.js work? It's a no go for me on modern, but more to the point, why are we explicitly offering something in the preferences that is recommended against? Should it not be replaced with m:TemplateScript, or am I missing something? Pinging @TheDJ: as the last editor there. ~ Amory (u • t • c) 13:45, 5 February 2018 (UTC)
- @Amorymeltzer: This edit won't work to notify TheDJ. This one will. --Redrose64 🌹 (talk) 18:10, 5 February 2018 (UTC)
- @Amorymeltzer: If i disable it I'll get angry people chasing me. I don't feel like dealing with that. Deprecating and encouraging people slowly takes me too much time, which I don't have. —TheDJ (talk • contribs) 09:25, 6 February 2018 (UTC)
- I hear ya, and I don't by any means intend to impose my naïveté on your time, but does the gadget even function? I can't get the regex editor in vector or monobook either, and if it doesn't work I imagine nobody is using it. ~ Amory (u • t • c) 11:24, 6 February 2018 (UTC)
- It exposes some global functions, that people are supposed to use in their common.js file to add functionality.. It's an incredibly outdated design and hard to figure out how many people depend on this, but it's definitely quite a few. —TheDJ (talk • contribs) 13:45, 6 February 2018 (UTC)
- I hear ya, and I don't by any means intend to impose my naïveté on your time, but does the gadget even function? I can't get the regex editor in vector or monobook either, and if it doesn't work I imagine nobody is using it. ~ Amory (u • t • c) 11:24, 6 February 2018 (UTC)
- @Amorymeltzer: If i disable it I'll get angry people chasing me. I don't feel like dealing with that. Deprecating and encouraging people slowly takes me too much time, which I don't have. —TheDJ (talk • contribs) 09:25, 6 February 2018 (UTC)
- I have an idea.. we can hide it, so that new people cannot enable it any longer... —TheDJ (talk • contribs) 13:46, 6 February 2018 (UTC)
- For the record, implemented in Special:Diff/824291173. —andrybak (talk) 12:57, 13 July 2024 (UTC)
Discussion at MediaWiki talk:Common.js § Class-triggered gadgets
You are invited to join the discussion at MediaWiki talk:Common.js § Class-triggered gadgets. – SD0001 (talk) 16:38, 25 January 2024 (UTC)
- For the record, this was archived at MediaWiki talk:Common.js/Archive 23#Class-triggered gadgets. —andrybak (talk) 12:55, 13 July 2024 (UTC)
The table of available gadgets
I think it would probably be a good idea to remove the table of available gadgets from this information page. The table is horrendously out of date and has been tagged as needing an update since 2010. It is missing several of the most commonly used gadgets (like twinkle) and contains several discontinued or removed gadgets (e.g. the teahouse gadget). Despite MediaWiki:Gadgets-definition asking that all gadgets be added to the list this very obviously hasn't been done. Finally this table largely duplicates the functionality of a special page that is automatically generated by the software, Special:Gadgets, which contains a sorted list of all available gadgets, a short description of what they do and a link to their source files. I think it would be better to replace this table with a paragraph explaining that users can browse available gadgets in their preferences page, and that a list of all gadgets can be found on the special page. 192.76.8.91 (talk) 13:45, 8 July 2021 (UTC)
- OK, done. — xaosflux Talk 14:28, 8 July 2021 (UTC)
- Implemented in Special:Diff/1030149941/1032610278. —andrybak (talk) 13:01, 13 July 2024 (UTC)
Shortdescr gadget does not work on Tewiki with Vector-2022 UI
Request help to fix the Shortdescr gadget on Tewiki with Vector-2022 UI. It works fine in traditional Vector UI. Arjunaraoc (talk) 04:41, 27 August 2022 (UTC)
- @Arjunaraoc see Wikipedia:Village_pump_(technical)#Is_there_an_update_to_Vector-2022_today/yesterday?. — xaosflux Talk 18:09, 27 August 2022 (UTC)
Criteria
@TheDJ: What does They have to be written to allow users to run without Javascript
mean? Since all a gadget does is add JavaScript and CSS, for users with JS disabled, all gadgets already "allow users to run without JS", by not being available to them. Does it mean the CSS should not cause problems for them, or something else? Nardog (talk) 00:22, 24 January 2024 (UTC)
- I think it means default gadgets should not required for the website to function, because the website should function with js disabled. Snowmanonahoe (talk · contribs · typos) 00:23, 24 January 2024 (UTC)
- That and there are style only modules that might expect javascript to load from another module. This is pretty rare however... maybe we should remove that again, it might cause more confusion that it will be worth. —TheDJ (talk • contribs) 08:22, 24 January 2024 (UTC)
- What about
[Default gadgets should:] Not be required for content to be readable, except for styles-only gadgets
? The current wording is confusing indeed, but on the other hand one can easily forget about no-JS users while developing a JS gadget, so it’s important to stress this. —Tacsipacsi (talk) 21:06, 24 January 2024 (UTC)- Sounds good, edited. Nardog (talk) 03:34, 26 January 2024 (UTC)
- For the record: Special:Diff/1199138145. —andrybak (talk) 13:01, 13 July 2024 (UTC)
- Sounds good, edited. Nardog (talk) 03:34, 26 January 2024 (UTC)
- What about
- That and there are style only modules that might expect javascript to load from another module. This is pretty rare however... maybe we should remove that again, it might cause more confusion that it will be worth. —TheDJ (talk • contribs) 08:22, 24 January 2024 (UTC)
Mobile view categories
I can't see them anymore. Where did they go? —hueman1 (talk • contributions) 03:44, 5 July 2021 (UTC)
- @HueMan1: You mean the gadget? It’s no longer necessary, the advanced mobile mode shows categories since recently. See also discussion on MediaWiki talk:Gadgets-definition. —Tacsipacsi (talk) 17:31, 5 July 2021 (UTC)
- @Tacsipacsi: The advance mode is so annoying. I wish there were more options to choose from. —hueman1 (talk • contributions) 17:34, 5 July 2021 (UTC)
- @HueMan1: while we retired the testing gadget, the code still exists at MediaWiki:Gadget-MobileCategories.js and you could mw.load it to your Special:MyPage/mobile.js. — xaosflux Talk 10:33, 6 July 2021 (UTC)
- Thanks, Xaosflux. I didn't know that this was possible, but it seems like I entered the code wrong. —hueman1 (talk • contributions) 11:15, 6 July 2021 (UTC)
- @HueMan1 and Xaosflux: I think it should be on Special:MyPage/minerva.js, not mobile.js, mobile.js is only for the MediaWiki namespace. —Tacsipacsi (talk) 23:06, 6 July 2021 (UTC)
- Thanks, Xaosflux. I didn't know that this was possible, but it seems like I entered the code wrong. —hueman1 (talk • contributions) 11:15, 6 July 2021 (UTC)
- @HueMan1: while we retired the testing gadget, the code still exists at MediaWiki:Gadget-MobileCategories.js and you could mw.load it to your Special:MyPage/mobile.js. — xaosflux Talk 10:33, 6 July 2021 (UTC)
- @Tacsipacsi: The advance mode is so annoying. I wish there were more options to choose from. —hueman1 (talk • contributions) 17:34, 5 July 2021 (UTC)
- @Tacsipacsi: mw:Manual:Interface/JavaScript says that it is for the "Mobile website". Now, that site happens to use Minerva so you should be able to do things there as well, but mobile.js is not limited to mobile users looking at pages in the mediawiki namespace as far as I'm aware (please point to any documentation that says otherwise and we can update the local description). — xaosflux Talk 23:17, 6 July 2021 (UTC)
- @Xaosflux: I mean only the mobile.js page that is specified in the MediaWiki namespace is loaded, not that the mobile.js page would be loaded only when seeing pages in the MW namespace (the latter would hardly make any sense). And no, the documentation you cited doesn’t say that Special:MyPage/mobile.js would be for the mobile website, there’s no such entry in the table in mw:Manual:Interface/JavaScript#Personal scripts. (§ Global scripts lists it, but that applies to the MediaWiki namespace version only, not to user subpages.) By the way, I looked at the code, and while it isn’t easy to prove that something doesn’t get loaded, I found nothing that would load /mobile.js. —Tacsipacsi (talk) 00:13, 7 July 2021 (UTC)
- @Tacsipacsi: ah OK, thank you :) so yes, @HueMan1: move that to User:HueMan1/minerva.js. — xaosflux Talk 00:28, 7 July 2021 (UTC)
- I added a note at MediaWiki:Mobile.js. — xaosflux Talk 00:33, 7 July 2021 (UTC)
- @Xaosflux and Tacsipacsi: It works now, thanks! —hueman1 (talk • contributions) 00:54, 7 July 2021 (UTC)
- For the record, the note was added in Special:Diff/1032366391. Custom JS for Special:MyPage/minerva.js is: —andrybak (talk) 13:18, 13 July 2024 (UTC)
mw.loader.load('/w/index.php?title=MediaWiki:Gadget-MobileCategories.js&action=raw&ctype=text/javascript'); // Backlink: [[MediaWiki:Gadget-MobileCategories.js]]
- I added a note at MediaWiki:Mobile.js. — xaosflux Talk 00:33, 7 July 2021 (UTC)
MediaWiki:Gadgets-definition
Should the sections for MediaWiki:Gadgets-definition begin with a capital letter? Qwerfjkl talk 21:53, 25 March 2021 (UTC)
- They're prepended with "MediaWiki:Gadget-section-" to produce page names which are then transcluded to Special:Gadgets and Special:Preferences#mw-prefsection-gadgets. For example, "browsing" becomes MediaWiki:Gadget-section-browsing → Browsing. This allows internationalisation. --Redrose64 🌹 (talk) 23:18, 25 March 2021 (UTC)
- There is also some documentation at mw:Extension:Gadgets#Sections. —andrybak (talk) 12:54, 13 July 2024 (UTC)