Wikitech-l November 2012

wikitech-l@lists.wikimedia.org

130 participants
133 discussions

jQuery 1.9 will remove $.browser (deprecated since jQuery 1.3 - January 2009)
by Krinkle 16 Nov '12

16 Nov '12

Hey all, Just a reminder that jQuery will (after almost 4 years of deprecation!) drop $.browser [1] in jQuery 1.9. Please check your scripts and make sure you are are no longer using "$.browser" (or "jQuery.browser"). After jQuery 1.9 is released, from the next MediaWiki deployment after that $.browser will be undefined and old code trying to access a property of it will throw a TypeError for accessing a property of undefined. Don't be alarmed, this has been a long time coming. It's been almost 4 years, and by the time this is deployed it will probably have been 4 years. For those who just realised their script is still using it, or if you read this later to fix someone else's script that just broke (hello future, did the world end in 2012?), I'll briefly describe two migration paths you can take from here: == Feature detection In most (if not all) cases of people using $.browser it is because they want different behaviour for browsers that don't support a certain something. Please take a minute to look at the code and find out what it is you are special-casing for that apparently doesn't work in a certain browser. Research on the internet and look for a way to detect this properly (examples below). Browser detection (instead of feature detection) is not reliable, nor is it very effective. For example, Internet Explorer has changed a lot since IE6. Blindly doing A for IE and B for non-IE isn't very useful anymore as most (if not all) of the new features will work fine in IE8, IE9 or IE10. The opposite is also true. If you do something cool for Chrome, you're missing other WebKit-based browsers that should get the same awesomeness (Safari, Chromium, iPhone/iPod/iPad, possibly Android, Flock, etc.) these all share the exact same engine that backs Chrome). And what if Firefox and IE also start to support this new awesome feature? There are many ways to do feature detection. jQuery comes with various detectors built-in in the object "jQuery.support"[2]. This contains for example "support.ajax", "support.opacity" and many more[2]. You can also easily make your own feature detector: * var supportPlaceholder = 'placeholder ' in document.createElement('input'); * var supportJSON = !!window.JSON; etc. If you need any help with feature detection, I'd recommend asking in one of the following channels on irc.freenode.net: * ##javascript (recommended) * #jquery * #wikimedia-dev == jQuery.client [3] If you can't figure out how to detect what you really want to switch for, there is an elaborate plugin in MediaWiki that does the same thing that jQuery.browser used to do (and more). This can be used as an alternative migration path. To give an impression: > jQuery.browser < { chrome: true, version: "22.0.1229.94", webkit: true } > $.client.profile(); < { name: "chrome", layout: "webkit", layoutVersion: 537, platform: "mac", version: "22.0.1229.94", versionBase: "22", versionNumber: 22 } For example: if ( $.browser.chrome ) {} Would become: ++ dependency: jquery.client var profile = $.client.profile(); if ( profile.name === 'chrome ) {} But: if ( $.browser.msie ) { // IE doesn't support opacity el.style.filter = 'alpha(opacity=50)'; } else { .. } Should become: if ( $.support.opacity ) { el.style.filter = 'alpha(opacity=50)'; } else { .. } Or better yet, since this is supported by jQuery core for a while now, like this: $(el).css('opacity', 0.5); Which will do the right thing for newer browsers and old IE respectively. -- Krinkle [1] http://api.jquery.com/jQuery.browser/ [2] http://api.jquery.com/jQuery.support/ [3] https://www.mediawiki.org/wiki/RL/DM#jQuery.client

5 5

HTTPS for all logged-in users (was: Re: secure.wikimedia.org is no more)
by Ryan Lane 16 Nov '12

16 Nov '12

> Awesome! Another old hack swept away. :D > > Do we have a timetable for migrating all login sessions to HTTPS yet? I > love that we've got a clean HTTPS option available, but it really skeezes > me out that we still allow logins and passwords over plain HTTP. > We're waiting on some MediaWiki development work for this. I think Chris Steipp and Roan Kattouw would probably know more. - Ryan

3 3

SVG-Edit community conference call December 4
by Brion Vibber 16 Nov '12

16 Nov '12

Marc Laporte of TikiWiki and some other folks are doing a push to revitalize the SVG-Edit project; we're going to have a conference call on December 4, 2012: https://code.google.com/p/svg-edit/wiki/CommunityConferenceCall This would be a great opportunity to bring up any potential issues that are blocking integration of SVG-Edit into MediaWiki and bringing it to production on Wikipedia sites. Here's the current SVGEdit extension for MediaWiki: https://www.mediawiki.org/wiki/Extension:SVGEdit Some sample issues: * safe round-tripping when editing existing files (automate some compatibility testing?) * i18n/l10n overhaul (there are localized UI strings, but needs love. Consider setting up on TranslateWiki?) * UI customizability (can/should we adjust the UI to fit the surrounding site better?) SVG-Edit is pretty much all client-side goodies, so on our end the main technical thing that needs doing before we can start actually testing it 'for reals' on production infrastructure is: * CORS support for upload.wikimedia.org < https://bugzilla.wikimedia.org/show_bug.cgi?id=28700> I know there's also some interest from the author of the TranslateSvg extension in SVG-Edit, there may be some other folks interested. :) -- brion

1 0

Off-and-on CSS and rendering issues, Bits related?
by Andre Klapper 16 Nov '12

16 Nov '12

There seem to be some off-and-on CSS issues (not always reproducible) that harm a lot of people and are likely interconnected to some extend. Please chime in if you have ideas. Pasting the list so far: * Page reload error "mw.getConfig is not a function" with Monobook: https://bugzilla.wikimedia.org/show_bug.cgi?id=42192 - mdale wrote that it "appears the resource loader is doing something strange, or at least inconsistent with debug mode and when vector skin is active." * Diffs not colored: https://bugzilla.wikimedia.org/show_bug.cgi?id=42193 * Missing Gadgets tab (also with Vector skin): https://en.wikipedia.org/wiki/Wikipedia:Village_pump_%28technical%29#Missin… * http://en.wikipedia.org/wiki/Wikipedia:VPT#Style_sheet_changes * Editing articles on mr.wikipedia has overlays issues for anon users, makes text unreadable (also with Vector skin): https://bugzilla.wikimedia.org/show_bug.cgi?id=42170 * "WikiEditor panel not loading": https://de.wikipedia.org/wiki/Wikipedia:Fragen_zur_Wikipedia#Fehlerhaftes_F… * Maybe also: Edit conflict sometimes does not show the current text: https://bugzilla.wikimedia.org/show_bug.cgi?id=42163 Speculation: Looking at the monthly stats on http://ganglia.wikimedia.org/latest/graph_all_periods.php?c=Bits%20applicat… (click on "Inspect") there is a drop of "Out" on November 5/6th. >From http://wikitech.wikimedia.org/view/Server_admin_log#November_5 : 21:54 aaron synchronized wmf-config/mc.php 'Switched all wikis to memcached-multiwrite.' 21:54 logmsgbot_: aaron synchronized wmf-config/InitialiseSettings.php 'Disabled spammy (with pecl memcached) memcached.log, the useful one is memcached-serious.' Also Reedy mentioned on IRC that "Peter did some bits apaches upgrades to 12.04 yesterday". Help welcome. (Thanks to RobLa for pointing to Ganglia and Bits there.) andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/

4 3

HTTPS Mobile en.wikipedia.org
by Derric Atzrott 16 Nov '12

16 Nov '12

My phone's homepage is set to https://en.wikipedia.org/ . Yesterday I noticed for the first time that the redirect to the mobile site sends you to http://en.m.wikipedia.org/ regardless of whether or not you used http or https to begin with. I'm not sure if this is the right list for this (as I'm not on any other lists, so I don't know their culture and scopes as well), but I believe that it is on topic. Thank you, Derric Atzrott Computer Specialist Alizee Pathology

2 1

Boston Devs! -- We're hiring!
by Thomas Fellows 16 Nov '12

16 Nov '12

Hey everyone, First, I apologize for the spam, so I'll keep it short - We're a Cambridge, MA based firm that's looking to change the world (yay!), and have 2 openings on our development team. We are developing all sorts of extensions for MediaWiki, and are looking to expand our team before our international launch! The full job listing is here, with more detailed info: http://boston.craigslist.org/gbs/sof/3398038106.html And if you have any questions or want further information, or just send me an email! Thanks, Tom

2 2

Welcome Quim Gil to Engineering Community Team!
by Sumana Harihareswara 16 Nov '12

16 Nov '12

I am very happy to announce that tomorrow is Quim Gil's first day in the Engineering Community Team of the Wikimedia Foundation. His title is Technical Contributor Coordinator (IT Communications Manager) which means that he'll be reaching out to and nurturing our testers, coders, documenters, product managers, sysadmins, and other contributors to Wikimedia technologies like MediaWiki. His blog entry about coming to WMF: https://flors.wordpress.com/2012/08/27/moving-up-in-the-freedom-stack/ Quim is a contributor to Catalan Wikisource & Wikipedia and English Wikipedia (User:Qgil), and has helped Wikimedia's mobile team as a volunteer. Most recently he's dug into statistical analysis of MediaWiki's coder community and the philosophical conundrum of RESOLVED:LATER. You might also know him from his activity in the worlds of GNOME, Qt, and Maemo -- he's coming to us from Nokia. If I try to detail all the consulting, event-running, volunteer recruiting, open source community management, writing, and projects he's done, I'll hit some kind of mailman limit so I won't try. :-) Quim lives in the Bay Area and will be working out of the San Francisco office while reporting to me remotely, which is kind of hilarious. In the near future he'll be encouraging volunteer testers and running our Outreach Program for Women. And tomorrow is Quim's birthday! So, happy birthday and welcome, Quim! -- Sumana Harihareswara Engineering Community Manager Wikimedia Foundation

6 5

IRC office hours with the Language Engineering team 2012-11-21 16:30 UTC
by Srikanth Lakshmanan (WMF) 16 Nov '12

16 Nov '12

Hello everyone, You're invited to the IRC office hours with the Language Engineering team[1] at the Wikimedia Foundation. Date: 2012-11-21 Time: 16.30 UTC Venue: #wikimedia-office Agenda: 1. Universal Language Selector updates. 2. Upcoming Language team test day 3. India events & Misc. For more logistical info and time conversion links check the page on Meta[2]. Thanks, and we hope to talk to you soon! [1] http://wikimediafoundation.org/wiki/Language_Engineering_team [2] https://meta.wikimedia.org/wiki/IRC_office_hours -- Srikanth L Wikimedia Language Engineering Team

1 0

(no subject)
by Sheel Sindhu Manohar 15 Nov '12

15 Nov '12

http://crossroadsfc.com/wp-content/plugins/google235.html

1 0

git, gerrit and git review
by dan entous 15 Nov '12

15 Nov '12

dear all, after struggling for quite some time on how to best work with the wikimedia gerrit site, i have created a page that i’m hoping will add some clarity for myself and others. while the documentation that already exists is helpful, i still found it difficult to understand, so i have done my best to summarize what i discovered and write the documentation from the point of view of someone who is more familiar a git workflow. if you have a moment, please take a look and edit or contribute to the page where necessary as i am definitely not a gerrit expert. http://www.mediawiki.org/wiki/Git/Gerrit with kind regards, dan

5 4

← Newer
1
...
5
6
7
8
9
10
11
...
14
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Wikitech-l November 2012