From Meta, a Wikimedia project coordination wiki
Jump to: navigation, search

Developer Wishlist Survey: propose your ideas[edit]

At the Wikimedia Developer Summit, we decided to organize a Developer Wishlist Survey, and here we go:

The Wikimedia technical community seeks input from developers for developers, to create a high-profile list of desired improvements. The scope of the survey includes the MediaWiki platform (core software, APIs, developer environment, enablers for extensions, gadgets, templates, bots, dumps), the Wikimedia server infrastructure, the contribution process, and documentation.

The best part: we want to have the results published by Wednesday, February 15. Yes, in a month, to have a higher chance to influence the Wikimedia Foundation annual plan FY 2017-18.

There's no time to lose. Propose your ideas before the end of January, either by pushing existing tasks in Phabricator or by creating new ones. You can find instructions on the wiki page. Questions and feedback are welcome especially on the related Talk page.

The voting phase is expected to start on February 6 (tentative). Watch this space (or even better, the wiki page) - SSethi_(WMF) January 21st, 2017 3:07 AM (UTC)

Global.js not loading consistently[edit]

For a couple of weeks now, I think since the update of two weeks ago, my global (and local) .js scripts are not executing consistently. I'm on Chrome, and Ctrl-Shift-R sometimes (but not always) helps. Things work fine on my iPad using Safari. Any thoughts? StevenJ81 (talk) 14:18, 16 March 2017 (UTC)

@StevenJ81:: See for how to debug. --Malyacko (talk) 14:34, 16 March 2017 (UTC)
Thank you, @Malyacko. Any idea what I should even be looking for? StevenJ81 (talk) 14:37, 16 March 2017 (UTC)
I'm a bit late, but this also is/was happening to me too. If I remember correctly warping everything in functions helped. --TerraCodes (talk) 22:10, 11 April 2017 (UTC)
Hi StevenJ81. You're likely hitting a race condition, so depending on how large the page is, some code may be firing/initializing before the page is actually ready, causing problems. I'm experiencing the same issue intermittently. Adjusting the user scripts you're using to wait for the page to be fully ready before the user scripts start would likely fix the issue you and I are having. --MZMcBride (talk) 00:12, 12 April 2017 (UTC)
Krinkle says using mw.loader.using() should do it. --MZMcBride (talk) 00:46, 12 April 2017 (UTC)

Expansion of $fax macro in translations to RTL languages[edit]

When I translate a page that contains $fax macro into a right-to-left language (See this example), the translated page arranges the expanded $fax macro (or template or whatever its called) with its digits incorrectly placed (See the second bullet list item on this translated page section as example). I think the solution might be to embed a pair of paragraph direction markers inside the body of $fax so that the LTR languages would not be affected while all RTL languages would be corrected. Or as a workaround please help me to know how to wrap the $fax itself in the translated statement so that it is displayed correctly. Alfa80 (talk) 15:48, 20 April 2017 (UTC)

Consider wrapping the fax number in <div style="direction:ltr;">(number)</div>. And for good measure replace any spaces with non-breaking spaces. StevenJ81 (talk) 16:50, 20 April 2017 (UTC)
Thanks a lot, the direction is fixed now using that markup, but the number appears in its own new line. I used non-breaking spaces before and after div section.Alfa80 (talk) 10:46, 21 April 2017 (UTC)
If span works, you might not have the separate line issue. StevenJ81 (talk) 17:36, 21 April 2017 (UTC)
Yes check.svg Great!, thanks, <span dir=rtl>, did the trick.Alfa80 (talk) 17:58, 22 April 2017 (UTC)