User talk:Krinkle/Archive 1

Merge of Review queue and Requests for comment

Hi. I've reverted your merge of Review queue and Requests for comment. I see them as distinct processes with distinct goals, so it doesn't make any sense to me why they'd be merged. I also couldn't find any discussion of this merge. Let me know if you have any questions or concerns. --MZMcBride 20:06, 20 February 2011 (UTC)Reply

I merged them in respond to a then active mailing list thread. Looking back I think either could work, but right now neither is used. Most of that shouldn't be on-wiki anyway in my opinion. Bugs that should get done are filed on BugZilla, given an assignee (and a priority perhaps) and wait for execution, listing them on mw.org doesn't help anything. Ideas for extensions, that have been written, can be submitted to SVN and if WMF needs them, a bug can be opened to request installing it on WMF which means it will be reviewed first in CodeReview. Anyway, if you believe they are better apart, I can understand that approach as well. Thanks, Krinkle 13:50, 24 February 2011 (UTC)Reply

Extra buttons for new-fangled toolbar

Gday Krinkle. We talked in IRC last week about buttons for Wikieditor toolbar, and you said that you were working on stuff to make it easier for the technically (less|in)-competent like me to fathom how to do buttons. If I was meant to be looking somewhere for any works with regard to this, then I missed out on where to look. If there is nothing to see, that is okay, and I will await any forthcoming announcement with bated breath. :-) — billinghurst sDrewth 15:17, 13 June 2011 (UTC)Reply

Hey there,
Don't worry, you didn't miss it. I'll publish it on my Meta-Wiki scripts folder later tonight (thuss replacing the no-longer-optimally-working "insertVectorButtons"). Thanks for the reminder. Krinkle 15:19, 13 June 2011 (UTC)Reply
  Done m:User:Krinkle/Scripts/InsertWikiEditorButton. Krinkle 21:30, 13 June 2011 (UTC)Reply

Purge action script

I left a note at Talk:Snippets/Purge action#Vector support? for you. It's related to m:Tech#Special:ListFiles. --MZMcBride 03:21, 25 August 2011 (UTC)Reply

Thanks for the note. Replied there. Krinkle 11:51, 25 August 2011 (UTC)Reply

Menu-Tabs toggler

Hi Krinkle. I have the animation sorted now. But I'd love to hear your opinion on the script as a whole. It is now a gadget on enwiki, or you can import it from en:User:Edokter/MenuTabsToggle.js. What is left on my wishlist is to find out if addPortletLink has some callback functionality that I can hook into, as the only problem remaining is that portlet links added to empty portlets afterwards are not included. Edokter (talk) — 12:51, 4 September 2011 (UTC)Reply

r97381

Have you seen my comment to r97381? --Fomafix 19:34, 15 October 2011 (UTC)Reply

I've seen it now. Fixed in rev:99935. Thanks! Krinkle 23:52, 15 October 2011 (UTC)Reply

Enhanced clock gadgets

Hi Krinkle,

I made some enhancements to the clock gadgets on french wikibooks :

  • Add support for clockWithSeconds parameter in user script to show/hide seconds,
  • Restart clock display at hh:mm:ss.100 (100ms within the next second) to avoid skipping some seconds display.

See :

--DavidL 14:27, 10 December 2011 (UTC)Reply

API talk:Meta

Why did you deleted this page? KPu3uC B Poccuu 13:32, 19 January 2012 (UTC)Reply

I meant to blank the page not to delete it. Hereby restored. The reason I wanted to blank it is because your account was blocked on a Wikipedia site and blacklisted under "cross-wiki vandalism". When going through cross-wiki activity I came across this creation here on MediaWiki.org and it didn't seem to be very useful or sense-making. Anyway, restored it and left a note. Perhaps you can clarify the problem or confirm that it was indeed not a stupidity in the API ? Krinkle 22:38, 19 January 2012 (UTC)Reply
What? I has never been blocked for vandalism on any of Wikimedia sites. I was 3 times blocked on Russian Wikipedia but never for vandalism and never on other sites. Please show me a log entry where I was blocked for "cross-wiki vandalism". KPu3uC B Poccuu (talk) 12:12, 21 February 2012 (UTC)Reply

Review request

Hi!

Could you please review my changes in the documentation about the (enhanced) toolbar customization? (to make sure I've used RL and dependencies correctly). Helder 15:06, 2 February 2012 (UTC)

BTW: maybe those changes are aplicable to m:User:Krinkle/Scripts/InsertWikiEditorButton.js? Helder 13:32, 22 February 2012 (UTC)
Hi, I understand your change but I'm not sure it's right. I think it's the job of the WikiEditor to make sure it's enabled correctly and available depending on the user and/or site configuration. Checking this preference here and loading the module seems redundant and/or using undocumented or unintended "features". Roan and Trevor recommended and documented samples with checking for $.fn.wikiEditor to decide whether or not to execute button-adding code for WikiEditor and that seems to work fine. Was there any reason (other than precaution) for this change? On the other hand I can imagine race conditions where we might want to add buttons to the load queue before MediaWiki has started loading the WikiEditor. I'll get back to you on this one! Krinkle (talk) 15:05, 22 February 2012 (UTC)Reply
Thanks!
It was just for precaution, since its being recommended to always declare dependencies of scripts and gadgets...
I reverted part of you edit because of bugzilla:34594. Helder 15:44, 22 February 2012 (UTC)

Delete

Hi, could you please delete this – test edit by anonymous user. Thanks, --Mikołka 17:29, 7 February 2012 (UTC)Reply

Thanks,   Done. Krinkle 18:00, 7 February 2012 (UTC)Reply

Documentation for gadget authors

We're trying to start a library for gadget authors to use. Please check it out and post any questions or comments there. -- MarkAHershberger(talk) 01:43, 9 March 2012 (UTC)Reply

Version number

MediaWiki is now at MediaWiki 1.18.2, so can you upgrade Template:MW stable release number? Thanks! --Jeffw(talk) 00:09, 23 March 2012 (UTC)Reply

Thanks,   Done Krinkle (talk) 21:17, 23 March 2012 (UTC)Reply

Template:WikimediaDownload edit

Hi, In response to your recent revert on Template:WikimediaDownload (diff), I'd like to alert you that while the ExtensionDistributor is back, it still is only working with SVN and as a result Users will miss out on the new versions of these that are hosted on Git as well as be unable to download new extensions that are only hosted on Git, I myself have an extension that is only in Git.

I understand the problems with the direct link, but until the ExtensionDistributor is updated, don't you think we should leave in a link to download a snapshot from Git? Thanks. Khaled El Mansoury (talk) 11:47, 13 May 2012 (UTC)Reply

Git search

Hi!

I was wondering if there is any replacement for your tool which works with trunk version of MW, which is in Git/Gerrit? Helder 19:57, 17 May 2012 (UTC)

I wanted to start on this a few weeks ago. But unfortunately, the Toolserver had HTTPS issues making it impossible to create a regular git clone of the mediawiki repository (TS-1369). Now that the main issue has been fixed, I can work on this. Krinkle (talk) 20:12, 17 May 2012 (UTC)Reply
Great! :-D Helder 21:09, 17 May 2012 (UTC)
I just found out this feature on top right of the gerrit interface.
BTW, using it I found out some ues of wgMWSuggestMessages, which doesn't seems to be defined anywere. Helder 15:08, 6 July 2012 (UTC)
We've got search on mediawiki.org as well ;-) Special:Search/wgMWSuggestMessages -> Manual:Interface/JavaScript. It has been deprecated, and removed in MediaWiki 1.16. That mwsuggest.js script has also been deprecated, but not removed yet. Krinkle (talk) 20:15, 8 July 2012 (UTC)Reply

getAllRights

Hi!

I saw this edit and was wondering if the list of rights is/could be made available for user scripts and/or gadgets. I ask because of this bug. Helder 13:23, 21 May 2012 (UTC)

As mentioned in the diff there, it is already possible in PHP for Core and Extensions. Hence the RL2 project didn't have to do anything for that. The Gadgets 2.0 project also needed this information in the front-end, but that's not on the task list because that is already possible in core as well:
I see the linked Github issue talks about not wanting to use an AJAX request. Well, that's not going to work. But you shouldn't be worried about that imho. Krinkle (talk)
Thanks. Do you mean not to worry about a new AJAX request or about checking "if the user has the 'delete' user right"? Helder 20:13, 21 May 2012 (UTC)
The http request. Krinkle (talk) 20:14, 21 May 2012 (UTC)Reply

A barnstar for you!

  The Original Barnstar
For being the most active sysop. -- Cat chi? 21:40, 27 May 2012 (UTC)Reply
Thanks! Krinkle (talk) 21:44, 27 May 2012 (UTC)Reply

Adding pages of special characters to WikiEditor toolbar

Hi!

Do you think this approach is appropriated? Is there a better solution, or this is good enough to stay in the documentation? Helder 20:35, 31 May 2012 (UTC)

Branch points historical?

I'm not sure the page Branch points is really "historical", as you have marked it. It's still being updated and being used in {{MWReleases }}, which in turn is being used on MediaWiki 1.20. - dcljr (talk) 00:48, 3 June 2012 (UTC)Reply

Thanks, I've updated it with new links for Git. The ability to transclude it within the wiki is useful so lets maintain this for now. Krinkle (talk) 01:15, 3 June 2012 (UTC)Reply

MediaWiki:Edittools.js

Hi, you renamed the page above without leaving a redirect behind, but there are many pages currently linking to it. Could you please recreate the redirect? Capmo (talk) 01:44, 10 June 2012 (UTC)Reply

There's only very few links left actually (I've fixed a few more just now). And the name has no significance, it has no special meaning. It was just the local name of a script loaded manually from Common.js. The delete reason contains a link to the new location. Thanks, Krinkle (talk) 11:02, 10 June 2012 (UTC)Reply

Template:Note

Dear Krinkle. I commented on your recent changes on the Note template . I merly pointed out my opinion and I did not change anything back. I think that in some cases you are going to fast in changing or implementing templates. I like the ExtensionInstall template but we should preserve any documentation history like in Extension:WikiEditor. We lost the following lines:

In 1.16, the WikiEditor was part of the usability initiative. As such, to get it for 1.16, please download it from Special:ExtensionDistributor/UsabilityInitiative or 1.16 svn branch.

For 1.17, get the extension with distributor or svn and drop it into MediaWiki directory /extensions (for example, it will create the new folder /extensions/WikiEditor)

For 1.18 and later the extension already comes with your MediaWiki package. You only need to install and configure it as described below:

When you use the latesed Wiki software this is not a problem but some or a lot of people still use "older" versions of MediaWiki. Do not get me wrong, I appriciate the work you do on the MediaWiki Wiki but don't forget that most of the time things are the way they are for a reason. You can change and improve the documentation on this Wiki but a lot of people all around our globe are reading and using the same documentation, don't forget that. Best regards, --Felipe de Jong (talk) 11:59, 2 July 2012 (UTC)Reply

I removed that because the version branched at 1.16 as part of the UsabilityInitiative is unstable and was not the version in use on Wikipedia at the time of 1.16wmf4 deployment. It should not be used. Also 1.16 is no longer supported, not even as legacy. The 1.17 and 1.18+ versions are okay, widely used and those don't need different instructions. I've replied on the Note template on its talk page. Krinkle (talk) 12:14, 2 July 2012 (UTC)Reply

Asking to do the REPLY button on the kk wiki!

Hello Krinkle!

Can you help us to do in the Kazakh wikipedia the button Reply in the user talk or finding for us the man who can do it. (example Talk:MediaWiki)

with regards, --Polat Alemdar (talk) 17:29, 5 September 2012 (UTC)Reply

That is Extension:LiquidThreads. Requests for installing it go on Bugzilla (Wikimedia > Site configuration). Krinkle (talk) 18:01, 5 September 2012 (UTC)Reply

Regarding substitution of welcome template

Hi, Timo. I was substituting the template because welcome templates should always be substituted. However, since you objected, I will stop. Also, I can use my bot to unsubstitute the template (but I need to apply for a bot flag first so as not to flood recent changes). --Meno25 (talk) 13:06, 17 September 2012 (UTC)Reply

That is a page on Wikipedia not MediaWiki.org. I don't know why the Welcome template on Wikipedia "always needs to be substituted", but I do know that the Welcome template we have here on MediaWiki.org doesn't. Krinkle (talk) 13:11, 17 September 2012 (UTC)Reply

Bugzilla:39268

Gday Krinkle. Wondering whether I can impose on you to have a look at Bugzilla:39268 which is having a large nuisance effect at the Wikisources. A change somewhere in 1.20wmf9 now prevents the use of toolbar formatting in the headers and footers, and instead applies all the formatting to the main body when in Page: ns. eg. Thanks if you are able to look at it, and more thanks if you are able to resolve it. — billinghurst sDrewth 14:44, 3 October 2012 (UTC)Reply

I've left a message on the bug report, I'll look further when I have more time/information. Meanwhile, perhaps we can trade. Could you vouch to have the (in my opinion, horrible) big red IP-warning greatly, greatly, reduced to a much less scary impression? Thanks, Krinkle (talk) 15:50, 3 October 2012 (UTC)Reply

Mediawiki:Common.js -> MediaWiki:Gadget-site.js

Hi Krinkle. I was attempting to fix the mediawiki:common.js file on a corporate wiki today, got frustrated, and decided to burn it down and start from scratch. When I came here to Mediawiki.org to grab their file as a starting point, I discovered that it was gone/moved to MediaWiki:Gadget-site.js (by you, obviously). All of my googling turned up no chatter at all about this restructuring and all of the documentation still mentions and links to the old file name, so I'm puzzled as to your reasons for doing this. Should I be moving the common.js files on all of my wikis? Etc. Thanks! ~Michael Chidester (talk) 20:28, 2 January 2013 (UTC)Reply

Me too, could you please leave a brief explanation why MediaWiki:Common.css is now at MediaWiki:Gadget-site.css? Thx --Rogerhc (talk) 23:32, 9 February 2013 (UTC)Reply

Please do not copy other wiki's local configuration as a starting point. Most (if not all) of MediaWiki:Common.css (now at MediaWiki:Gadget-site.css) is specifically for the MediaWiki.org wiki. Everything that is needed for the starting point is stored on the server side in the skin and core modules, they are not stored in the local MediaWiki namespace. Your wiki should do just fine without anything in there.
If there is some specific template or interface feature on MediaWiki.org that you don't see on your own wiki that you'd like to copy, please figure out what it is and import it accordingly but don't blindly copy random stuff, it won't do you any good.
If/when you do import something, just import it to your MediaWiki:Common.css (unless you have the Gadgets extension installed and know how to use it). Krinkle (talk) 13:28, 12 February 2013 (UTC)Reply

Using collapsable remote toggle in a template

Hi, I was looking for a way to make Template:ApiEx collapse example output by default, but couldn't find a way so that the [expand] button is on the left side, possibly custom formatted. The remote toggle works ok, but since the template is used multiple times on the same page, it requires unique ID which I couldn't generate inside a template. Thanks! --Yurik (talk) 07:24, 10 January 2013 (UTC)Reply

Backtalk

Hi. Thanks for the great feedback and I'll be working to fix things as quickly. In the nonce I responded on your "other" talk page.RiverStyx23 (talk) 23:54, 18 January 2013 (UTC)Reply

Parallel uploads

Regarding API:Etiquette and bugzilla:44584, are parallel uploads via the commons api permissible? Smallman12q (talk) 21:02, 2 February 2013 (UTC)Reply

I don't know. I'd recommend asking in a central channel instead (Project:Support desk, IRC or wikitech-l). Krinkle (talk) 13:33, 12 February 2013 (UTC)Reply

Open external links in new window

Hi Krinkle, I copied your snippet (mediawiki.org/wiki/Snippets/Open_external_links_in_new_window) to Arabic Wikinews because published articles have a template with social bookmarks which should preferably open in a new window. However, it only opens links to external sites in a new window in uneditable pages, such as page history or user contributions pages, but not in articles. I would prefer it to be the other way round :) Have I done anything wrong? Could you please check it? You will have to enable the option yourself because I do not know how to enable it by default (I believe it should be). It is in the last tab of your preferences at Arabic Wikinews, last item in middle group. Thank you. --PICAWN(talk) 18:30, 4 March 2013 (UTC)

Gadgets 3.0

Hi!

Would you mind fixing any mistakes I did when I documented what I think is in the scope of the (future) Gadgets 3.0? Helder 22:59, 11 March 2013 (UTC)

mwSnapshots dead?

Hi. The links to mwSnapshots at Nightlies don't seem to work for me lately. :-( --MZMcBride (talk) 21:40, 22 April 2013 (UTC)Reply

Works for me. Does it work now? Perhaps Toolserver was down in general. Krinkle (talk) 05:26, 23 April 2013 (UTC)Reply
Weird. I was getting a 404 yesterday and a few days ago. It's working now, though. Thanks for taking a look. --MZMcBride (talk) 16:10, 23 April 2013 (UTC)Reply

hi I have replied on https://www.mediawiki.org/wiki/Extension_talk:MaintenanceShell#JavaScript_enabled_but_not_working 86.171.33.224 21:07, 16 May 2013 (UTC)Reply

Gadget-UTCLiveClock.js

Hi Krinkle,

I added a message about MediaWiki_talk:Gadget-UTCLiveClock.js#Improvment_of_the_clock_gadget, explaining that a fixed delay wont fix the problem.

--DavidL (talk) 13:50, 25 May 2013 (UTC)Reply

Extension:Echo

hi when was Extension:Echo last updated because you edit it and said the latest master download requires mediawiki 1.22 81.129.84.113 09:56, 26 May 2013 (UTC)Reply

I don't know. I do know that the current iteration of Echo requires 1.22. If you download Echo from the 1.20 or 1.21 branch you'll have the latest version from before 1.22 development started. Krinkle (talk) 09:57, 26 May 2013 (UTC)Reply

Gadgets and CSS load order

I notice that CSS from gadgets through RL is loaded before CSS from MediaWiki:Common.css. This can create problems with specificality, as some gadgets are used to override CSS from Common.css, which requires hacks like !important;. Is there a way to force gadget CSS to be loaded after Common.css, ie. by listing Common.css (module name?) as a dependency? Edokter (talk) — 11:31, 26 May 2013 (UTC)Reply

Extension:Echo

hi how can I install Extension:Echo I have managed to install it and it shows the grey circle with 0 on it next to user name but when I click it it goes to the special notification page how can I when I click on it it shows the ntofication flyout please the website is here [1] 81.129.84.113 12:57, 26 May 2013 (UTC)Reply

Please refer to Extension talk:Echo or BugZilla. I don't maintain this extension and am not the person to help you with this. Krinkle (talk) 20:07, 26 May 2013 (UTC)Reply

I didn't know that Echo was dependent on mediawiki.ui version

I've tested Echo on the same versions of MediaWiki used by Wikipedia and MediaWiki.org, and I got the original version working on MW 1.20, so I assumed it's functionality was tied to the MW version release, but not exactly why.

I saw where you rejected my change, added the appropriate information, and cleared up my confusion.

Thank you.

Arcane21 (talk) 16:24, 26 May 2013 (UTC)Arcane21Reply

Memory leak in $.makeCollapsible

Hi there :) You seem to be the author and maintainer of the $.makeCollapsible code. Would you take a look at this bug report, please? Pecoes (talk) 10:47, 16 June 2013 (UTC)Reply

Thanks. Krinkle (talk) 17:17, 17 June 2013 (UTC)Reply

TemplateData and the new WikiProject module

Hi Krinkle! Thanks for all your hard work on TemplateData and the Visual Editor - it looks like it will be awesome when it is finished. I discovered TemplateData the other day, and we have been talking about it in relation to a new WikiProject meta-module for the English Wikipedia. Eventually we want this module to replace w:en:Template:WPBannerMeta, which is transcluded on something like 4 million talk pages over there. (The template is too complex to make it a drop-in replacement, though - this is going to be a complete rewrite.) In particular, we have been wondering about how to deal with third-party tools that interact with WikiProject templates, such as Kephir's Rater.

TemplateData looks like an ideal solution for those kinds of tools as well, but at the moment it doesn't allow all the data fields that we need. For example, we would need a way to say that a parameter depends on having other parameters set, and a way to specify all possible values that a parameter can take. (It would be really neat to be able to generate a drop-down list of possible values, especially as those values can vary quite considerably between WikiProjects.) This process could be made quite easy if there were some default types for parameters, e.g. boolean, item in a pre-defined list, or freeform text. It would also be great to be able to group parameters together, so that it would be easy to see what parameters were for task force x, and what were for task force y, etc.

Are there any plans to make this kind of data parse-able by TemplateData? I assume this would also be useful for the Visual Editor, so I think this would be a big plus for the WMF as well. But I would be interested to hear your thoughts on this regardless, as TemplateData will have large implications for how this WikiProject meta-module will eventually work. Best regards — Mr. Stradivarius ♪ talk ♪ 10:55, 20 June 2013 (UTC)Reply

Main Page Design

Hello. Could you explain how to create main page like on MediaWiki.org, please? It would be great if you explain step by step. 84.204.22.130 09:44, 24 June 2013 (UTC)Reply

Sorry, I can't. I didn't create it and it seems too complex to easily explain if you don't already know how to copy it. The only way (which is both easy to understand and also what an expert would have to do unfortunately) is recursively copy all the templates it uses (start on Main Page). You shouldn't have to reproduce the exact template structure because it is pretty much MediaWiki.org-specific. You'll have to learn how the HTML and CSS work and create your own version independently. Trying to copy the source will likely not do what you want, though you're welcome to try. Krinkle (talk) 21:44, 24 June 2013 (UTC)Reply
@84.204.22.130: Please see Thread:Project:Support desk/Frames like on mediawiki frontpage. jonkerz ♠talk 22:43, 24 June 2013 (UTC)Reply

Reporting problem

Hi I would like to report a problem on https://toolserver.org/~krinkle/mwSnapshots/#!/mediawiki-core/master this because it keeps saying snapshot index temporarily unavalible please try again later please fix it 109.144.247.60 19:46, 11 July 2013 (UTC)Reply

Patrolling

Hello Krinkle!

Very nice of your part start discussing patrolling efforts in wikimedia projects. Some time ago I started trying to understand how is the workflow of counter vandalism at pt.wiki (my home wiki) and I noticed that we have a lot of gaps in your effort to vanish vandalism. I analyzed every tool we had and noticed some important points:

  • Only huggle and rollback can patrol all edits reverted. RTRC permits open the page to use rollback but other gadgets don't take advantage of editor's flag to patrol all edits reverted.
  • There's no "patroll all edits" button. There's a bug opened to implement this but I don't know the status.
  • Fastbuttons don't patrol pages when we apply a label to speedy deleted process or no source tag even if the user has rights to do so.
  • I'd like to bring to your attention this graphic which was made to measure how many edits are passing by or live patrol efforts. Unfortunately, there's a huge gap since Fastbuttons and another gadget we use a lot don't patrol.

Thank for all your help with RTRC which is an excellent to that I'm trying to make popular at pt.wiki. And thank you again for your efforts to improve counter vandalism efforts at all wikis.OTAVIO1981 (talk) 12:39, 12 August 2013 (UTC)Reply

Nederlands

Eindelijk iemand die nederlands spreekt hier op MediaWiki!  Josse.Cottenier(+) (Talk | Contribs) 09:15, 14 August 2013 (UTC)Reply

Adding content to the top of the wiki

$out->AddInlineScript() doesn't work for Google AdSense banners since the function already includes the script tags and the last part of the code is inside the script tags. It should use $out->PrependHTML(), which seems to work fine for adding banners or anything else, if anyone else has a similar question.

Is there any particular way to make the added code appear above the page title instead of below it? ఠ_ఠ Inquisitor Sasha Ehrenstein des Sturmkrieg Sector (Talk) (Contr) 06:08, 17 August 2013 (UTC)Reply

Gadget-collapsibleTables

Maybe you missed my message on MediaWiki talk:Gadget-site.js#Collapsible tables. If I haven't missed anything, MediaWiki:Gadget-collapsibleTables.js shouldn't be needed anymore. --Ciencia Al Poder (talk) 09:21, 27 August 2013 (UTC)Reply

Both are still used and do different things. Krinkle (talk) 00:15, 28 August 2013 (UTC)Reply

Gadgets across projects

Hi Krinkle, I would like to have your comments about my idea for project m:Grants:IEG/Visual editor- gadgets compatibility. Helder pointed out in talk page that you had a similar (in some manner) project called Le Tour de Wikí. Thanks, Eran (talk) 17:52, 30 September 2013 (UTC)Reply

Requests for comment/Configuration database

Hi, Requests for comment/Configuration database is being considered as one of the RFCs to be discussed at the RFC review on 2013-11-06 via IRC. You are receiving this notification because you edited or discussed this RFC. We hope to see you there.--Qgil (talk) 00:32, 5 November 2013 (UTC)Reply

Upload presentation

Hello Krinkle, Can you upload the presentation you gave last Saturday during the conference? Please add it to the category Commons:Category:WCN 2013 on Commons. Probably best to upload it in pdf. Thanks! Romaine (talk) 01:25, 7 November 2013 (UTC)Reply

Intuition on Labs

Hello, is Intuition documented/recommended anywhere nowadays? The only page I found is tswiki:Intuition, while it should be recommended on wikitech:Nova Resource:Tools/Help at the very least. Considering that hundreds of tools accounting for some 98 % of Toolserver traffic still have to be migrated, it would be important and most efficient for the migrators to support i18n too from the first day. --Nemo 12:21, 26 November 2013 (UTC)Reply

It's not advertised anywhere as the recommended framework for localisation on Tool Labs. However, documentation for the code itself lives in the repository (on GitHub) as mentioned on tswiki:Intuition: https://github.com/Krinkle/TsIntuition/wiki/Documentation. Krinkle (talk) 13:04, 26 November 2013 (UTC)Reply
I'm currently working on migrating the OrphanTalk2 tool from Toolserver as a showcase for how to use Intuition in Tool Labs. After that is done, I will update the documentation accordingly. If you're currently working on a migration as well and need instructions earlier, feel free to ping me privately and I'll try to get you set up. Krinkle (talk) 13:04, 26 November 2013 (UTC)Reply
Eating your own dogfood and then making docs sounds good, thanks. If you don't have time to do it soonish, maybe you could ask some other Intuition user: I think some tools on Labs still use it, don't they? --Nemo 13:19, 26 November 2013 (UTC)Reply

mediawiki.Uri

hi.

in this commit, (done a couple years ago), you changed the comment at the top of the file: the comment demonstrates code that changes the hostname from 'foo.com' to 'www.foo.com'. (compare the lines starting with // anchor with id 'id1' now links to between previous file and your commit. same for "id2") for some reason, this comment was changed such that it seems as if the code does not do what one expects it to do (i tried to test it, and the code actually does do it - the issue here is the comment). i guess it was a nistake - could you please fix it? it seems awfully petty, but this comment have cost me about 10 minutes trying to figure what don't i understand here...

peace - קיפודנחש (talk) 20:34, 23 December 2013 (UTC)Reply

Thanks! I've submitted Gerrit #Ifeaf71. 21:43, 23 December 2013 (UTC)

Snapshots hasn't been updated

Hi please update page https://toolserver.org/~krinkle/mwSnapshots/#!/mediawiki-core/master because it hasent been updated to Mediawiki 1.23 Wmf 13. Please update it. 2.221.61.175 13:31, 8 February 2014 (UTC)Reply

Hi, Please use https://tools.wmflabs.org/snapshots/ instead from now on. I'll set up a redirect soon. Krinkle (talk) 06:28, 10 February 2014 (UTC)Reply

problem downloading mediawiki

hi it seems there is a problem at https://tools.wmflabs.org/snapshots/#!/mediawiki-core/master it wont let you download any of the files on there it comes up with errors 90.195.251.120 15:29, 12 February 2014 (UTC)Reply

Thanks! Looks like one of the directories got detached. The 404 Not Found errors are gone now. Krinkle (talk) 23:40, 12 February 2014 (UTC)Reply

Snapshots only has master branch, please fix it

hi this https://tools.wmflabs.org/snapshots/#!/mediawiki-core/master site only shows master it doesent show any of the wmf releases please fix it. it only shows master. it doesent show any of the wmf released nor the mediawiki version you have released. 86.135.249.17 19:23, 17 February 2014 (UTC)Reply

  Fixed. Bug in the git-config caused other branches not to be fetched. Fixed now. Thanks! Krinkle (talk) 11:07, 19 February 2014 (UTC)Reply
thanks for fixing it 86.135.250.124 12:09, 19 February 2014 (UTC)Reply

Follow moodbar?

Hi Krinkle, i asked a question on the Dutch Wiki "Help" page (see here) Can you provide me with a solution/answer? Regards Saschaporsche (talk) 11:02, 24 February 2014 (UTC)Reply

The thread has been archvied to Help:Helpdesk/Archief/feb_2014 on nl.wikipedia.org. Looks like it has been handled. Krinkle (talk) 00:07, 5 March 2014 (UTC)Reply

MediaWiki 1.23wmf15 missing from snapshots

Hi Mediawiki 1.23 Wmf 15 isent on here https://tools.wmflabs.org/snapshots/#!/mediawiki-core/master. It doesent update to the newer Wmf release. And please add Wmf 16. 176.24.9.44 17:22, 27 February 2014 (UTC)Reply

Thank you for reporting. I've found the error in the snapshots update log. It is related to bug 44129. I'll see what I can do. Krinkle (talk) 17:32, 27 February 2014 (UTC)Reply
ok thanks 176.250.150.202 15:43, 28 February 2014 (UTC)Reply
  Fixed Krinkle (talk) 00:05, 5 March 2014 (UTC)Reply
thanks for fixing it. 90.204.133.243 14:57, 5 March 2014 (UTC)Reply

https://tools.wmflabs.org/snapshots/ problem

hi this https://tools.wmflabs.org/snapshots/ has not been updated in over 18 hours even though it says it runs every hour. 86.135.251.50 19:38, 1 May 2014 (UTC)Reply

Thanks. Looks like the crontab got corrupted. Fixed. Krinkle (talk) 22:08, 1 May 2014 (UTC)Reply

Snapshots not updated in 27 hours

Hi https://tools.wmflabs.org/snapshots/#!/mediawiki-core/master this has not been updated in 27 hours. please could you fix it. 151.225.137.145 20:46, 31 July 2014 (UTC)Reply

Seems something got corrupted again. I guess it's really pushing the limits of what Git, Linux and the file system can handle with a repository this big. Somehow it always manages to get stuck after a few weeks. I've cleaned up and reset some things and it seems fine again now. Thanks for the notice! Krinkle (talk) 19:48, 1 August 2014 (UTC)Reply

jquery.textSelection.js (tiny bug?)

Greetings Krinke, as I looked for some undocumented JS funktions, I saw a strange code block IMO, see the next 5 lines after line 379 here. The "if" and "else" are the same! Or I'm wrong? Best -- Perhelion (talk) 12:01, 8 August 2014 (UTC)Reply

Hi Perhelion,
This code is relatively old and I can't say for sure how it would behave if altered. The two branches appear to set the same properties to the same values indeed. They do, however, execute the statements in a different order. This may be of significance since the properties may have immediate effect. If (like the comment in the code says) there is a known browser bug with selections being removed if start is beyond end, it's important to set them in the right order so that both are used (instead of the end being ignored, and start being set without an end).
However this is just a guess. You're welcome to submit a patch or report a bug for it. Then we can try it out and see how it behaves in currently supported browsers. --Krinkle (talk) 23:27, 29 August 2014 (UTC)Reply

Snapshots

Hi it seems that snapshots hasent been updated in 54 hours. please fix it. 86.173.55.212 11:55, 14 August 2014 (UTC)Reply

  Done. Looks like for some reason, every few weeks git fetch origin stops working from the Labs grid, after I do it manually once it works again. Will investigate further. Fixed for now. Krinkle (talk) 11:30, 20 August 2014 (UTC)Reply

Interlanguage links

Hi, I don't know if this the correct place for a suggestion that imo would improve the Wikipedea layout. So please forgive me if I'm totally in the wrong place :) I would consider it an improvement if the Interlanguage links would also be visible on the creating page after you click a red link. That way when an article with that title is not yet created in your language, you could easily switch to another language in which the article already is been written. 82.75.176.92 20:39, 7 September 2014 (UTC)Reply

Editing filters

When editing filters, please make sure you keep the logic intact. (See wikt:Special:AbuseFilter/history/24). --Wikitiki89 (talk) 19:14, 16 September 2014 (UTC)Reply

Template:MW src

I've created this template and I saw your edit. What's your suggestion about that? Where can I link to the "library"? Best regards - Fabsouza1 (talk) 20:45, 2 December 2014 (UTC)Reply

@Fabsouza1: In this edit, I removed the use of Template:MW src, as there is already a link to the source code of the file in the Template:MW file header. As of writing, it links to the source code of that file in the "master" branch and for the "1.24.0" and "1.23.7" releases. An additional link seemed superfluous in my opinion. Krinkle (talk) 00:00, 3 December 2014 (UTC)Reply

Unwatch from watchlist script

Hello, thanks for this great script (Unwatch from watchlist). I had one question though, is there a way to adapt the code so that it becomes a one-click action, instead of taking you to a different page to confirm you really want to unwatch the article? I would personally find it more useful if I could just click it, without having the leave the watchlist. Thanks, --Midas02 (talk) 13:01, 16 December 2014 (UTC)Reply

@Midas02:   Done, diff. --Krinkle (talk) 03:31, 17 December 2014 (UTC)Reply
Great! Much obliged, --Midas02 (talk) 11:25, 20 December 2014 (UTC)Reply

Random acts of CR barnstar

 
I hereby award you this random acts of code review barnstar for being among the few most active +2'ers that we know of! Nemo 23:34, 3 February 2015 (UTC)Reply
@Nemo: Thank you! --Krinkle (talk) 05:27, 6 February 2015 (UTC)Reply

A kitten for you!

 

Have a nice week!

:-)

Helder 19:47, 10 March 2015 (UTC)Reply

@Helder: Thanks! It was a nice week   --Krinkle (talk) 18:08, 17 March 2015 (UTC)Reply

Starting conversion of LiquidThreads to Flow at mediawiki.org

(Hi Krinkle. I know that you already know, so I'm just adding this here for completism, and for any of your page-watchers. :)

Hello. I'm sending this to you, because you've been one of the top 50 users of LQT on mediawiki.org over the last 360 days,[2] and I wanted to make sure that you'd seen the announcement at Starting conversion of LiquidThreads to Flow at mediawiki.org. There are links in the topic-summary at the top, for other discussions (wikitech-l and Project:Current_issues), and a link to the planned process and timeline (scheduled to begin April 6, with smaller conversions at first). Please do test Flow out at Talk:Sandbox if you haven't tried it recently, and give any feedback/suggestions/requests at that main discussion location. Much thanks, Quiddity (WMF) (talk) 00:33, 28 March 2015 (UTC)Reply

Template:Git file

Hi,

Thanks for fixing {{Git file }}. The fact is that I made a change before in order to fix the problem of the link generated by {{Git/pywikibot }} in Manual:Pywikibot/clean sandbox.py in the top right of the page. So, would you have an idea to solve this problem? Thank you Automatik (talk) 01:27, 4 June 2015 (UTC)Reply

@Automatik: The problem for Pywikibot is that it is trying is trying to include page names into Git file names. That's fine if they match, but they don't. The Pywiki repository has underscores in file names, whereas the page name has spaces. This has nothing to do with "url escaping" or "git" in general. It's just something specific to Pywiki. Please fix this inside the Pywiki template by replacing the space with an underscore (or use the whole filename as parameter). Escaping all file name inputs in Template:Git file would break hundreds of other mediawiki.org pages. Krinkle (talk) 09:48, 4 June 2015 (UTC)Reply
I'd suggest to use {{FULLPAGENAMEE}} instead of {{FULLPAGENAME}}, but that doesn't fix the problem, because it's used inside {{#titleparts: }}, and the strange thing is that #titleparts: changes underscores to spaces! --Ciencia Al Poder (talk) 14:24, 4 June 2015 (UTC)Reply
@Automatik: Fixed, revision of Template:Git/pywikibot. Krinkle (talk) 14:53, 4 June 2015 (UTC)Reply
Thank you so much! Automatik (talk) 16:00, 4 June 2015 (UTC)Reply

Consultation

Hi Krinkle, how are you? We need your help on es.wp. This gadget doesn't work since yesterday (resourceloader migration), and we have the same problem with this other gadget. We have tried some things, but we have no idea what the problem is, can you help us? Thanks in advance.--Syum90 (talk) 21:24, 8 August 2015 (UTC)Reply

@Syum90: It seems w:es:MediaWiki:Gadget-CorrectorOrtografico.js was already fixed by He7d3r. Let me know if you're still having issues with w:es:MediaWiki:Gadget-DetectaDesambiguaciones.js. –Krinkle 01:23, 8 September 2015 (UTC)Reply
Well, I don't know if the problem continues, I've contacted with -jem-, who manages the gadgets on es.wp. Thanks.--Syum90 (talk) 15:34, 8 September 2015 (UTC)Reply
Hi again, problems with w:es:MediaWiki:Gadget-DetectaDesambiguaciones.js have been already solved. Thanks and regards.--Syum90 (talk) 10:14, 22 September 2015 (UTC)Reply

Fix mw snapshot

Hi visting https://tools.wmflabs.org/snapshots/#!/mediawiki-core/master it shows the last dump as 1553 hours ago. Please fix it Paladox2017 (talk) 17:01, 10 August 2015 (UTC)Reply

Thanks. The auto-update stopped because of a Labs outage last month (which also commented-out the auto-restart crontab). Back online now. Krinkle (talk) 05:44, 11 August 2015 (UTC)Reply

enclose="div"

Heiya Krinkle, over the years I added enclose="div" to quite a lot of pages. I guess this is something for a bot to clear. I am sure that you know somebody who controls a bot able to do this. Alternatively it might be good to add a task to Phabricator? Cheers --[[kgh]] (talk) 16:18, 3 September 2015 (UTC)Reply

@Kghbln They're harmless/ignored now. I wouldn't worry about it. (Perhaps similar to Image vs File.) Just know that it's no longer used and is best omitted for new contributions. Krinkle (talk) 16:33, 3 September 2015 (UTC)Reply
Indeed, but sometimes housekeeping is not a bad idea at all. When being asked I do always recommend this to people. That's what bots are good for. :) Still nothing utmost important. So for the time being I will remove this en passant. Cheers --[[kgh]] (talk) 21:43, 3 September 2015 (UTC)Reply

Compatibility

Hi Krinkle, reading the description of "Grade C", it seems that these are the browsers where we actively provide a JavaScript-free experience. In other words, the browsers tested for here. But the table in that section didn't reflect that at all. Does my change to that page make sense? This, that and the other (talk) 08:50, 16 November 2015 (UTC)Reply

@TTO: I understand what you mean, but it was intentionally written that way because it is important that our Grade C experience works in modern browsers as well. Adding an "end" version to Grade C seems confusing to me and only duplicates information in the table. Also, there are various scenarios in which a modern browser can enter this mode and we actively need to ensure that this is working correctly as well. I've rephrased it but essentially reverted your edit for this reason. –Krinkle 00:51, 17 November 2015 (UTC)Reply
OK, so long as the table and the prose don't contradict each other, I am happy. (Although I see that you haven't edited the page yet.) One issue I did have with what was there before is that, say, Firefox 20 was listed as a Grade C browser, meaning it receives a JS-free experience, which is apparently not true. It is really Grade X. This, that and the other (talk) 01:01, 17 November 2015 (UTC)Reply
@TTO: Also, the edit wasn't entirely accurate. We don't support arbitrarily old versions. So "Firefox versions prior to 3" is an inaccurate statement because Grade C is active support with prioritised handling of bug reports. Whereas issues for Firefox 1 are not prioritised. We don't support Firefox 1. The current system will serve it Grade C as attempt, but that's merely an implementation detail. –Krinkle 01:02, 17 November 2015 (UTC)Reply
@TTO: Good point about Firefox 20. That should indeed implicitly fall under Grade X. I'll think about it some more. Thanks! –Krinkle

Congratulations

Congrats. :) [3] Nemo 18:05, 24 November 2015 (UTC)Reply

Snippets/Hide prefix in category

Hi! Happy New Year ;)

This snipped causes a strange effect in the translatable categories. See example in Category:Pywikibot/pt vs Category:Pywikibot - if hidden prefix is equal to the full pagename, this page is displayed "As Is" in the base category only, but in the translation categories is displayed language postfix instead (for Manual:Pywikibot/pt - "/pt", in this example). --Kaganer (talk) 18:11, 9 January 2016 (UTC)Reply

Kaganer,
The snippet just provides a generic mechanism for hiding the first few characters of a title. It is in no way intended to be a definitive way of providing a list of readable page titles related to a subject. You may want to create a dedicated list for that on the central page about that subject. As for the localisation suffixes, that's an artefact of the Translate extension. Page titles on most MediaWiki sites don't have those suffixes. You may want to create a task in the Phabricator issue tracker for the Translate extension, asking for a way to render localised display titles in category listings. Also consider using Extension:DynamicPageList, which could help auto-generate a list on a page (instead of using the Category index as an overview page). –Krinkle 18:19, 31 January 2016 (UTC)Reply

Hochladen einer neuen Version eines Videos (höheren Bitrate)

Hallo Krinkle,

könntest Du mir einen Gefallen tun: ich habe beim erstmaligem Konvertieren eines Videos die Standardeinstellungen verwendet und würde jetzt gern für:

https://commons.wikimedia.org/wiki/File:20100930_xl_Hermann_Scheer_Neue_Energie_fuer_linke_Alternativen_Keynote_power_to_the_people_rls_on_green_tour_scheer-100930_lowres.webm

eine neue Version mit einer höheren Bitrate hochladen, die aber fast 1GB groß ist. Selbst kann ich nur 100MB als neue Version hochladen.

Ich habe den Tipp bekommen, die neue Version über Google-Drive bereit zu stellen und einen Admin zu bitten, sie auszutauschen. Wäre sehr nett, wenn Du das übernehmen könntest?

https://drive.google.com/file/d/0B_Jd5XwDZXusS1k5UFk1WDlfQmM/view?invite=CKO7lBI&ts=569bc52b

Mir ist dies wichtig, weil ich das Video für ein historisches Dokument halte: https://de.wikipedia.org/wiki/Hermann_Scheer

Viele Grüße

--Molgreen (talk) 19:56, 22 January 2016 (UTC)Reply

Gadgets definition skins parameter

Hi! Does the skins= parameter on MediaWiki:Gadgets-definition work for you? It doesn't work for me. I tried with skins=minerva here. I also couldn't find a way to get to the gadget part of the preferences menu on the mobile interface. Nirmos (talk) 14:14, 22 April 2016 (UTC)Reply

A barnstar for you!

  The Technical Barnstar
Thanks for the sample. I improved it using http_build_query. Baudet (talk) 10:43, 5 May 2016 (UTC)Reply

Rollback function changes

Hello Krinkle, would you mind popping in to en:Wikipedia:Village_pump_(technical)#Rollback_function_has_been_changed and offer any suggestions? Thank you, Xaosflux (talk) 23:43, 26 May 2016 (UTC)Reply

fixIEScroll

On many projects, there is code that looks like this:

/* Scripts specific to Internet Explorer */

if (navigator.appName == "Microsoft Internet Explorer") {
    /** Internet Explorer bug fix **************************************************
     *
     *  Description: Fixes IE horizontal scrollbar bug
     *  Maintainers: [[User:Tom-]]?
     */
    
    var oldWidth;
    var docEl = document.documentElement;
    
    function fixIEScroll() {
        if (!oldWidth || docEl.clientWidth > oldWidth)
            doFixIEScroll();
        else
            setTimeout(doFixIEScroll, 1);
        
        oldWidth = docEl.clientWidth;
    }
    
    function doFixIEScroll() {
        docEl.style.overflowX = (docEl.scrollWidth - docEl.clientWidth < 4) ? "hidden" : "";
    }
    
    document.attachEvent("onreadystatechange", fixIEScroll);
    document.attachEvent("onresize", fixIEScroll);
    
    
    /**
     * Remove need for CSS hacks regarding MSIE and IPA.
     */
    
    if (document.createStyleSheet) {
        document.createStyleSheet().addRule('.IPA', 'font-family: "Doulos SIL", "Charis SIL", Gentium, "DejaVu Sans", Code2000, "TITUS Cyberbit Basic", "Arial Unicode MS", "Lucida Sans Unicode", "Chrysanthi Unicode";');
    }
    
    
    //Import scripts specific to Internet Explorer 6
    if (navigator.appVersion.substr(22, 1) == "6") {
        importScript("MediaWiki:Common.js/IE60Fixes.js");
    }
}

Can this safely be removed? Nirmos (talk) 16:15, 8 June 2016 (UTC)Reply

Hi Nirmos: Yes, mostly. There are actually three pieces of code here: fixIEScroll, "MSIE IPA", and "IE60Fixes".
The code for fixIEScroll is safe to remove (line 4-28 above).
The code for loading IE60Fixes is safe to remove (line 37-42 above).
I am not familiar with the code for IPA overrides and I usually leave it (line 30-36 above).
Depending on whether a wiki has the IPA part, you can remove the "if appName" block completely. I usually use the following edit summary:
Maintenance: The wiki software no longer runs JavaScript in IE6 or IE7 - [[mw:RL/MGU#IE]]
Thanks for asking! --Krinkle (talk) 16:59, 8 June 2016 (UTC)Reply
Thank you very much. Nirmos (talk) 18:07, 8 June 2016 (UTC)Reply

My editinterface request

A user (Majora) is requesting confirmation from a MediaWiki developer that the updates I'm doing are necessary. If you want my help, you can go to m:Steward_requests/Global_permissions#Global_editinterface_for_Nirmos. Nirmos (talk) 01:55, 20 June 2016 (UTC)Reply

Gadget-LocalLiveClock.js

Can you check this topic? --ValterVB (talk) 14:07, 18 August 2016 (UTC)Reply

Filtering JavaScript gadgets server-side?

Many JavaScript gadgets are only used on a certain page, or in a certain namespace or during a certain action. Would it make sense to do this filtering server-side? Nirmos (talk) 07:21, 29 August 2016 (UTC)Reply

Unrecognized module names

Is it absolutely necessary that all JavaScript breaks when ResourceLoader sees an unrecognized module name? Why can't the gadget referencing the unknown module simply be skipped and a warning be added to console.log? Nirmos (talk) 14:24, 15 October 2016 (UTC)Reply

Sorry for the intromission. I don't know the full details, but I'd say, report a bug about that, providing steps to reproduce. --Ciencia Al Poder (talk) 17:47, 16 October 2016 (UTC)Reply

Intuition::getLangNames

On GitHub documentation, getLangNames is a public interface:

An edit in March changed public getLangNames to protected getLangNames on line 659 (now 661).

Code located in

Edit causes bug in TranslateSVG

Glrx (talk) 23:02, 18 October 2016 (UTC)Reply

@Glrx: Thanks, this was fixed last month in 4e7e5182. --Krinkle (talk) 21:05, 27 November 2016 (UTC)Reply

Extension:Gadgets

Hello. Based on this edit, may I ask, when the option will work as documented, because now it is not working: |rights=hidden is needed to be put in addition to |hidden, and this rules out the opportunity to use it with |default option. Jack who built the house (talk) 11:34, 27 November 2016 (UTC)Reply

Found phab issue, works after deploying 1.29.0-wmf.4, thank you. Jack who built the house (talk) 17:12, 2 December 2016 (UTC)Reply

"Remove top/bottom queue distinction"

Also, in light of this phab issue and this edit can you explain what repercussions it will have—we on ruwiki are using top queue to load the gadget that adds administrator flags to user nicknames. It gains us about 0.5 seconds (as I measured) in comparison to bottom queue and makes text jumps on page less perceptible. This is a problem because we have lots of users everyday clicking "revert" links by accident because of these jumps. Jack who built the house (talk) 11:47, 27 November 2016 (UTC)Reply

@Jack who built the house: Do not worry! The new combined queue is the same as the old "top" queue. Your gadget will work fine. Krinkle (talk) 21:04, 27 November 2016 (UTC)Reply

Help

I don't know if you'll be able to help me with this, but my local script on Wikipedia and global script is not loading completely on Chrome, Firefox, IE, and Edge. It affects Chrome the most. I tested it on my phone since it has Safari, and I didn't notice any problems sometimes. I also tested this on another computer, and I have the same problems from the other computer. 1989 (talk) 01:49, 21 March 2017 (UTC)Reply

MediaWiki:Gadget-contribsrange.js

Hi Krinkle. I hope you spent a beautiful time. I come to your talk page 'cause I can't read some gadgets on this page. Accessing to my Error Console Navigator I see this error: "TypeError: 'undefined' is not an object (evaluating 'ucfrm.month.selectedIndex')" and a link to MediaWiki:Gadget-contribsrange.js. I'm not sur if you can do something with this or you know somebody can help me dealing with this little problem. Thank you and best regards, Jmvkrecords (talk) 18:24, 15 June 2017 (UTC).Reply

@Jmvkrecords: Thanks. I don't normally have "MediaWiki:Gadget-contribsrange.js" enabled, but I tried it for you on es.wikipedia.org and found the issue. The errors are now Fixed. Let me know if it works! --Krinkle (talk) 19:44, 15 June 2017 (UTC)Reply
It is perfect now. Thank you so much Krinkel :) Jmvkrecords (talk) 23:14, 15 June 2017 (UTC).Reply

Question on the use of Category Depth in a DynamicPageList

Hi Krinkle, I have a question on the use of Category Depth in a DynamicPageList. I have developped a new Main Page for Dutch WikiNews in the incubator (scheduled for reopening at nl.wikinews.org on next Wednesday). I asked my question here. Could you please help me with this problem or mention a name of someone that can solve this? I have asked quite some persons yet and no-one knows the solution. Thanks in advance! Ymnes (talk) 14:13, 3 July 2017 (UTC)Reply

jQuery 3 enabled on Wikimedia wikis

Hi Krinkle,

Do you know the exact date(s) when jQuery 3 will be enabled? Contributors/Projects/Accessible editing buttons will still be moving during August, and I'd like to not have both changes landing on the same week(s). I can postpone relevant bits of the OOjs UI deployment to work around you – it's really no trouble at all – so please let me know what your schedule is. Whatamidoing (WMF) (talk) 19:13, 5 July 2017 (UTC)Reply

@Whatamidoing: I don't have an exact date yet. I'm aiming for early August (depends on the Beta Cluster roll-out). It would roll out with the train deployment of any given week. Thinking about this a bit, I'd actually like to consider intentionally having these happen at the same time (with the jQuery 3 deprecation warnings rolling out slightly earlier, if needed). The reason being that the jQuery 3 changes are largely deprecation-only, no breaking changes. As such, lots of editors looking for problems with their user scripts surrounding the edit buttons is an awesome opportunity for them to also discover these deprecation warnings – given most edits probably don't look in the "developer console" of their browser very often. However, I do understand if this is exactly what you're trying to avoid (e.g. potentially these warnings may be confusing when not related to edit buttons). On the other hand, it will likely break their scripts eventually (edit button-related, or otherwise) if they don't migrate them in time. (There is not yet a deadline for the removal of this deprecated jQuery functionality – I'm estimating at least a year). Thoughts? --Krinkle (talk) 22:01, 5 July 2017 (UTC)Reply
We've spread out the work on the accessible editing buttons because that spreads out the workload for script maintainers somewhat. (There are only so many people like User:TheDJ, but hundreds of wikis.) If you don't expect jQuery 3 to break anything (yet), then I'm willing to have them happen at the same time. How early could you enable jQuery 3? We've got most of the Wikipedias (including enwiki and dewiki) scheduled for 18 July, and all the non-Wikipedias except Commons scheduled for the first of August.
User:Ladsgroup took fawiki through the change earlier. It required a lot of changes. User:Matma Rex changed the implementation, and then he and User:Tar Lócesilion took plwiki through it with fewer changes needing to be made. 24 hours ago, we did five big Wikipedias plus Meta, and nobody's pinged me about any problems yet. So it's possible that it's not going to break many scripts now. Whatamidoing (WMF) (talk) 18:17, 6 July 2017 (UTC)Reply
Update: We're putting Commons on the schedule for Monday, 20 August. Whatamidoing (WMF) (talk) 22:00, 26 July 2017 (UTC)Reply

Reusability and scaling

Thanks for reminding us what's the point of FLOSS at Wikimedia_Developer_Summit/2018/Participants. It always worries me when we abandon something shared with others and make our own thing. Your work on the other points is also very appreciated; it so often feels that we're going backwards, even with relatively minor things such as phabricator:T110353, where past work goes wasted. --Nemo 15:03, 3 December 2017 (UTC)Reply

@Nemo: Thanks! --Krinkle (talk) 20:02, 2 February 2018 (UTC)Reply

Can you please add this package on packagist?

Hi, the following page suggests that you are the maintainer of the vendor 'mediawiki' on packagist.org. Can you please add this package: https://github.com/wikimedia/mediawiki-extensions-GoogleAnalyticsMetrics

MediaWikiModuleStore:{wgCookiePrefix}

Hi! It was my understanding that all JavaScript code was cached in localStorage in a key called MediaWikiModuleStore:{wgCookiePrefix}. That definitely was the case when I made sv:Special:Diff/40675087 on August 10 2017. Now I can't see any such key in localStorage. Has anything changed since then, and if so, is this intended? Nirmos (talk) 09:14, 6 September 2018 (UTC)Reply

It is still the case. The key is still in the format you describe, via mw.loader.store.getStoreKey(), and is still set in localStorage. I checked on sv.wikipedia.org as well, and I see the key being set. Is there a particular problem you are investigating? --Krinkle (talk) 16:45, 6 September 2018 (UTC)Reply
No, there is no particular problem I'm investigating. I was just wondering why I can't see it.
In Chrome, I can see it, both in the Application tab and if I write localStorage.getItem( mw.loader.store.getStoreKey() ) in the console.
In Firefox, I cannot see it, neither in the Storage tab, nor if I write localStorage.getItem( mw.loader.store.getStoreKey() ) in the console. It just returns null in Firefox. I have tried this on many different projects, thinking that perhaps svwiki had too much local JavaScript to be allowed to store it in localStorage (phab:T66721), but even on a project with minimal local JavaScript like Swedish Wikisource (minimal Common.js, four gadgets, of which only one is default) it still just returns null in Firefox.
Just thought I'd let you know. Nirmos (talk) 23:06, 6 September 2018 (UTC)Reply
Yes, it has been disabled for Firefox in 2016, and the loader-store optimisation is still disabled in Firefox today (per phab:T66721), because Mozilla bug 1064466 is still not resolved. If that bug is resolved in Firefox, we can enable the optimisation for Firefox! --Krinkle (talk) 23:58, 6 September 2018 (UTC)Reply
Wooow, so it's completely disabled in both Firefox and Opera. I had no idea. I was only aware of gerrit:216014. Thank you! Nirmos (talk) 01:06, 7 September 2018 (UTC)Reply
Yeah, although "Opera" in that context refers to Opera versions 12 and earlier. ResourceLoader does enable module storage for Opera 15 and later. (The bug that led to the disablement was part of the "Presto" engine, but Opera switched to the "Chromium Blink" engine in version 15 which does not have this bug). The old versions use the "Opera" UA-identifier, the newer versions use the "OPR/" identifier. MediaWiki does not enable JavaScript in Opera 12, so the check can be removed now. (change 1, change 2). --Krinkle (talk) 01:38, 7 September 2018 (UTC)Reply
But if it's now just the string "Firefox" you're looking for, why use a regex? Isn't that slow? Wouldn't it be faster with indexOf and compare with -1? Nirmos (talk) 02:50, 7 September 2018 (UTC)Reply
Return to the user page of "Krinkle/Archive 1".