Hi everyone!
Community Tech will be dealing a lot with technology relevant to Wikimedia
editors. We figured we'd introduce ourselves here, hoping some of you might
want to help out connecting us with the communities.
We're a new team within the Wikimedia Foundation, focused on meeting the
needs of active Wikimedia editors for improved, expert-focused curation and
moderation tools. Making the lives of the people who spend a lot of time
taking care of the Wikimedia projects a little bit easier. This is a small
team: myself, Frances Hocutt and Niharika Kohli, with some support from
Johan Jönsson as a Community Liaison. We'll focus on tasks that can be
dealt with quickly and that will have a direct benefit for the core
community and might be overlooked by the larger WMF development teams.
To find our feet, we’ve mainly been knocking out bugs during the first
weeks. At the moment, we're looking at tasks from previous surveys to see
how we can benefit the communities. We are also working on developing a
good process for soliciting new requests from the Wikimedians we're
responsible for helping. As part of this effort, we have written up a draft
proposal (
https://www.mediawiki.org/wiki/Community_Tech_team/Community_Wishlist_Survey)
for a cross-project community wishlist survey that we would like to launch
within the next month or two. Please take a look at the draft, share it
with your communities, and let us know your thoughts on the talk page.
You can find more information, such as the scope of the team, a roadmap,
what we're doing and what we've done so far on our team page:
https://www.mediawiki.org/wiki/Community_Tech_team
Ryan Kaldari
Engineering Manager, Community Tech
Hi all,
Just a quick thought occurred to me while I was working on the {{Template:User
wikipedia/Tech ambassador}} template for Wikipedia-en - is there anything
further we could do to promote the "group/project"?
I was thinking of maybe working on *Wikipedia:Tech Ambassadors*, but
thought I should get some comments from everyone else first before being
bold.
1. Does the Tech Ambassador program need promoting?
2. Is Wikipedia: namespace the correct/most appropriate place for a page
to exist?
Looking forward to your comments.
--
Samuel Tarling (User:Samtar on wp-en)
www.samtarling.co.uk
TL:DR; Double-check your wiki's site scripts and your personal scripts
to ensure "document.write" is no longer used.
Hey all,
We have strongly discouraged for many years the use of synchronous
"document.write()" to inject additional HTML into the output stream.
Across MediaWiki core, extensions, and gadgets this hasn't worked since 2012.
With two legacy exceptions: the 'site' and 'user' modules. We always found a way
to continue support for those. But this is now going to be removed.
In upcoming ResourceLoader upgrades and performance improvements, we will
cease support for synchronous document-write, in the site and user modules.
Use of document-write requires MediaWiki to instruct the browser to pause its
rendering before the browser may proceed to parse and display a page to users.
Even though most scripts don't use this feature, the mere fact that we support it
is causing a measurable impact on page load performance.
Starting in 1.26wmf17 (released to wikis this week), ResourceLoader will be
fully asynchronous. This change is already live on the Beta Cluster. [1]
This means it is no longer possible for the site and user scripts to, with
document-write, pause the browser execution and insert additional HTML in
the initial output stream.
Removing an API does not necessarily mean removing a capability. If you
encounter any issues or can't find a simple upgrade path for an existing
script, please reach out on the mailing list. Below is summary of a few
typical use cases:
1. Loading scripts.
Instead of `document.write("<script src=url></script>");`
use `mw.loader.load(url);` instead.
2. Loading stylesheets.
Instead of `document.write("<link rel=stylesheet href=url/>");`
use `mw.loader.load(url, "text/css");` instead.
3. Creating elements.
Instead of `document.write("<div>....</div>");`, use:
var nodes = $.parseHTML("<div>..</div>"); $('body').append(nodes);
Or something like:
$("<div>").attr({ "id": "foo" }).appendTo("body");
Please take some time to look through your wiki's site scripts (MediaWiki:Common.js,
MediaWiki:Vector.js, etc.) and make sure document-write is no longer used.
You can also use the search engine. For example:
https://nl.wikipedia.org/w/index.php?search=document.write&ns8=1https://commons.wikimedia.org/w/index.php?search=document.write&ns8=1
Search results from mwgrep on all public wikis:
https://phabricator.wikimedia.org/P1832
Check out the migration page for other deprecations and common issues you may encounter:
https://www.mediawiki.org/wiki/ResourceLoader/Migration_guide_(users)
== Further reading ==
The ResourceLoader improvements that led to this change are tracked under
https://phabricator.wikimedia.org/T107399.
Refer to the following workboards for other tasks in this area:
https://phabricator.wikimedia.org/tag/mediawiki-resourceloader/board/?order…https://phabricator.wikimedia.org/tag/performance-team/board/?order=priority
Now that the site and user modules are primary citizens in the ResourceLoader landscape,
their states can be tracked with mw.loader. This solves long-outstanding issues such as
https://phabricator.wikimedia.org/T106736 which sometimes caused malfunctions
in Common.js to affect user gadgets, VisualEditor, and other site tools.
— Krinkle
[1] http://en.wikipedia.beta.wmflabs.org/
Fixed, and deployed.
Thanks for reporting and sorry for not noticing that earlier.
— Krinkle
> On 5 Aug 2015, at 17:12, Max Semenik <maxsem.wiki(a)gmail.com> wrote:
>
> Already reported as https://phabricator.wikimedia.org/T108139 <https://phabricator.wikimedia.org/T108139>
>
> On Wed, Aug 5, 2015 at 5:10 PM, Bartosz Dziewoński <matma.rex(a)gmail.com <mailto:[email protected]>> wrote:
> I think this announcement is missing one important tidbit:
>
> If you have `document.write(…)` anywhere in your user JavaScript, **you will get a blank page**