[Wikitech-ambassadors] Re: WikiEditor translation update necessary

[Amir E. Aharoni]

I've approved your account! Thank you :)

בתאריך יום ו׳, 7 ביולי 2023, 16:28, מאת rtnF ‏:

> > If the "Completion" for your language shows anything less than 100%,
> please complete the translation.
>
> I received this notice while using Translate Wiki.
>
> > You need translation rights to translate messages.
> > Thanks for your translations :  You reached the translation limit for
> new translators. Our team will verify and upgrade your account soon. Then
> you will be able to translate without limits.
>
> On Fri, Jul 7, 2023 at 3:03 PM Amir E. Aharoni <
> amir.ahar...@mail.huji.ac.il> wrote:
>
>> Hi!
>>
>> TL;DR: The user interface localization of the WikiEditor extension needs
>> an update. Please check the state of your language at
>> https://translatewiki.net/w/i.php?title=Special:MessageGroupStats=ext-wikieditor
>> , and if the "Completion" for your language shows anything less than 100%,
>> please complete the translation.
>>
>> More details:
>>
>> The WikiEditor extension is the most commonly used interface for editing
>> wiki pages in wikitext ("edit source") on all Wikimedia wikis. For many
>> years, there was a technical issue with localizing it: for security
>> reasons, many of its messages could be translated only by administrators.
>>
>> This issue has recently been fixed by Jon Harald Søby (thanks!). Now all
>> of it can be translated by all translatewiki translators.
>>
>> In addition, several messages that had complex and repetitive HTML code
>> have been simplified as part of this update, and now it's generally easier
>> to translate them.
>>
>> Because of all these technical updates, the translation of the extension
>> needs to be updated. Usually such things don't warrant a special
>> announcement, but given that WikiEditor is such a central and prominent
>> component in the editing experience, I think it's justified this time.
>>
>> I recommend that experienced wiki editors who can write in languages
>> other than English go to
>> https://translatewiki.net/w/i.php?title=Special:MessageGroupStats=ext-wikieditor
>> , check the "Completion" column for their language, and if it's not 100%,
>> complete it.
>>
>> According to the usual deployment schedule, all the translations that
>> will be done before Monday morning (UTC) will be deployed between July 11
>> and July 13.
>>
>> If any technical support is necessary with using translatewiki, I'm happy
>> to help.
>>
>> Thanks again to Jon Harald for fixing this old bug, and thanks in advance
>> to all the wonderful volunteer translators!
>>
>> If you're curious about the technical details behind this bug, see:
>> * https://phabricator.wikimedia.org/T154891
>> * https://phabricator.wikimedia.org/T294760
>>
>> --
>> Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי
>> http://aharoni.wordpress.com
>> ‪“We're living in pieces,
>> I want to live in peace.” – T. Moore‬
>> ___
>> Wikitech-ambassadors mailing list --
>> wikitech-ambassadors@lists.wikimedia.org
>> To unsubscribe send an email to
>> wikitech-ambassadors-le...@lists.wikimedia.org
>>
> ___
> Wikitech-ambassadors mailing list --
> wikitech-ambassadors@lists.wikimedia.org
> To unsubscribe send an email to
> wikitech-ambassadors-le...@lists.wikimedia.org
>
___
Wikitech-ambassadors mailing list -- wikitech-ambassadors@lists.wikimedia.org
To unsubscribe send an email to wikitech-ambassadors-le...@lists.wikimedia.org

[Wikitech-ambassadors] WikiEditor translation update necessary

[Amir E. Aharoni]

Hi!

TL;DR: The user interface localization of the WikiEditor extension needs an
update. Please check the state of your language at
https://translatewiki.net/w/i.php?title=Special:MessageGroupStats=ext-wikieditor
, and if the "Completion" for your language shows anything less than 100%,
please complete the translation.

More details:

The WikiEditor extension is the most commonly used interface for editing
wiki pages in wikitext ("edit source") on all Wikimedia wikis. For many
years, there was a technical issue with localizing it: for security
reasons, many of its messages could be translated only by administrators.

This issue has recently been fixed by Jon Harald Søby (thanks!). Now all of
it can be translated by all translatewiki translators.

In addition, several messages that had complex and repetitive HTML code
have been simplified as part of this update, and now it's generally easier
to translate them.

Because of all these technical updates, the translation of the extension
needs to be updated. Usually such things don't warrant a special
announcement, but given that WikiEditor is such a central and prominent
component in the editing experience, I think it's justified this time.

I recommend that experienced wiki editors who can write in languages other
than English go to
https://translatewiki.net/w/i.php?title=Special:MessageGroupStats=ext-wikieditor
, check the "Completion" column for their language, and if it's not 100%,
complete it.

According to the usual deployment schedule, all the translations that will
be done before Monday morning (UTC) will be deployed between July 11 and
July 13.

If any technical support is necessary with using translatewiki, I'm happy
to help.

Thanks again to Jon Harald for fixing this old bug, and thanks in advance
to all the wonderful volunteer translators!

If you're curious about the technical details behind this bug, see:
* https://phabricator.wikimedia.org/T154891
* https://phabricator.wikimedia.org/T294760

--
Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי
http://aharoni.wordpress.com
‪“We're living in pieces,
I want to live in peace.” – T. Moore‬
___
Wikitech-ambassadors mailing list -- wikitech-ambassadors@lists.wikimedia.org
To unsubscribe send an email to wikitech-ambassadors-le...@lists.wikimedia.org

[Wikitech-ambassadors] Translatable modules

[Amir E. Aharoni]

Hi,

*Crossposting to Wikimedia-L, Wikitech-L, MediaWiki-L, and
Wikitech-Ambassadors. You can reply to the mailing list, but the ideal
place for further discussion is the talk pages of the wiki pages to which I
link below.*

There's a new proposal to localize Lua modules in a more modern, safe, and
convenient manner: https://www.mediawiki.org/wiki/Translatable_modules .

In the foreseeable future it will only affect multilingual sites, such as
Wikidata, Commons, Meta, and mediawiki.org, but at a later time it may also
be deployed on Wikipedias and other projects.

It will be great if experienced module developers could take a look at the
project page, https://www.mediawiki.org/wiki/Translatable_modules , and its
subpages, especially https://www.mediawiki.org/wiki/Translatable
modules/Proposed solutions . Your feedback will be very helpful in
implementing this project in a way that really benefits all the editors.

Thanks!

--
Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי
http://aharoni.wordpress.com
‪“We're living in pieces,
I want to live in peace.” – T. Moore‬
___
Wikitech-ambassadors mailing list
Wikitech-ambassadors@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-ambassadors

Re: [Wikitech-ambassadors] Fake or truth: blockchain (+ introduce myself)

[Amir E. Aharoni]

This is my impression as well: Everipedia is a project with rather unclear
goals, which seems to have more hype than substance at this point.

Another recent example of something like a "encyclopedia on a blockchain"
is Lunyr, which also looks like vaporware that doesn't deserve a lot of
attention.


--
Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי
http://aharoni.wordpress.com
‪“We're living in pieces,
I want to live in peace.” – T. Moore‬

2017-12-11 17:49 GMT+02:00 bawolff :

> Hi,
>
> So everipedia.com looks like some sort of Wikipedia fork/competitor.
> Larry Sanger is appearently involved with it (I guess he got bored of
> Citzendium). They seem to be a for profit company that wants to be
> more inclusionist than Wikipedia, and also raise money by selling
> customized articles.
>
> They appear to be advertising that they are doing something with
> "encylopedias" and "blockchain". However, they never specify what they
> are doing, there are no white papers or technical details, which is a
> good measure that something is BS.
>
> Probably they are trying to cash in on the hype around bitcoin.
> Blockchain is an ill-defined enough concept that you can make almost
> anything be "on the blockchain". Unless you are making a currency, it
> is usually a solution looking for a problem.
>
> This definitely has nothing to do with Wikipedia or Wikimedia.
>
> --
> Bawolff
>
> On Mon, Dec 11, 2017 at 3:04 PM, Dennis Tobar 
> wrote:
> > Hi everyone:
> >
> > I signed, the past week, the list of Tech Ambassador for Spanish
> Wikipedia.
> > My username is Superzerocool, a veteran user (over 12 years) in Wikimedia
> > movement, and in the real life I being an Engineer Informatic. I live in
> > Chile and I am currently part of the Board of Wikimedia Chile.
> >
> > In some chapter off-wiki talk (Telegram), an user share us a possibly
> > fake-news about the usage of blockchain to avoid the vandalism.
> >
> > As I see the article[1] (in Spanish), the news talks about Everipedia, a
> > startup related with Blockchain technology and how they use the
> blockchain
> > in English articles(?).
> >
> > As I see the article, the news is fake.
> >
> > Kindly,
> >
> > [1]
> > https://www.cuartopoder.es/innovacion/tecnologia/2017/12/
> 09/la-wikipedia-ya-no-se-podra-modificar-arbitrariamente-gracias-a-
> blockchain/
> >
> > --
> > Dennis Tobar Calderón
> > Ingeniero en Informática UTEM
> >
> > ___
> > Wikitech-ambassadors mailing list
> > Wikitech-ambassadors@lists.wikimedia.org
> > https://lists.wikimedia.org/mailman/listinfo/wikitech-ambassadors
> >
>
> ___
> Wikitech-ambassadors mailing list
> Wikitech-ambassadors@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-ambassadors
>
___
Wikitech-ambassadors mailing list
Wikitech-ambassadors@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-ambassadors

Re: [Wikitech-ambassadors] Tech News transitioning to the CEP team

[Amir E. Aharoni]

Thank YOU, Guillaume, for coordinating this so diligently, week after week.

Good luck to the new maintainers - it is transitioning to good hands!


--
Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי
http://aharoni.wordpress.com
‪“We're living in pieces,
I want to live in peace.” – T. Moore‬

2015-07-22 11:38 GMT-05:00 Guillaume Paumier gpaum...@wikimedia.org:

 Hello,

 I wanted to let you know that the Community Engagement (Product) team (CEP)
 [1] is going to gradually replace me as primary writer and coordinator for
 Tech News [2].

 When Tomasz Kozłowski (User:odder) and I started Tech News over two years
 ago,
 I didn't think it would grow to being translated to nearly 15 languages
 every
 week, or to being distributed to so many subscribers and community pages.

 Tech News was originally created as a way to connect the two communities of
 developers and content contributors, and I think it's done that job pretty
 well. In the meantime, the CEP team was created, and they have a very
 similar
 mission. They already manage very similar newsletters (like the one for
 VisualEditor) and it makes a lot of sense for them to also coordinate Tech
 News.

 I wanted to send this email to let you know about this change, so that
 you're
 not surprised when you start seeing emails about Tech News coming from the
 CEP
 team. Johan Jönsson (Johan/Julle) will be the primary point of contact for
 Tech News, and he'll also be working with Nick Wilson (Quiddity). I hope
 that
 you'll be as supportive to them as you have been to me over the years :)

 Which brings me to my last, and most important point: Thank you for all
 your
 help on Tech News over the past two years. Whether you helped me draft the
 newsletter, or you diligently translated it every week, or you notified
 your
 community about upcoming changes: I'm very thankful for the time you have
 dedicated to Tech News.

 I'll still be around on the mailing lists and the wikis during and after
 the
 transition, and I hope to continue to work with you on other projects.

 [1] https://meta.wikimedia.org/wiki/Community_Engagement_(Product)
 [2] https://meta.wikimedia.org/wiki/Tech/News

 --
 Guillaume Paumier
 Wikimedia Foundation

 ___
 Wikitech-ambassadors mailing list
 Wikitech-ambassadors@lists.wikimedia.org
 https://lists.wikimedia.org/mailman/listinfo/wikitech-ambassadors

___
Wikitech-ambassadors mailing list
Wikitech-ambassadors@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-ambassadors

Re: [Wikitech-ambassadors] [WikimediaMobile] Mobile Newsletter?

[Amir E. Aharoni]

Who is the target audience?

If I understand correctly, the target audience for the weekly Tech news and
the monthly VE news is experienced active editing Wikipedians (I don't know
if it was ever designated, but I am making an educated guess of the actual
practice).

But what is it for the mobile newsletter?
Active editing Wikipedians don't do it much on mobile AFAIK, although it
may be defined as the newsletter's goal to increase this number.

Wikipedia readers? There are many millions of those on mobile, but do they
read the newsletters? Certainly not on Village Pumps. Maybe it could be
delivered as a notification in the mobile web or in the apps?

What else?

New editors?
Projects' JS and CSS maintainers?
Gadget lovers?
Twitter aficionados?
Somebody else?

This target audience should be defined before starting to publishing it.

(N.B.: I didn't mention translation!!! :) )


--
Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי
http://aharoni.wordpress.com
‪“We're living in pieces,
I want to live in peace.” – T. Moore‬

2015-04-15 12:41 GMT+03:00 Moushira Elamrawy melamr...@wikimedia.org:

 Hello Mobile fans :)

 Florian and and myself earlier created a draft for a Mobile Newsletter:
 https://www.mediawiki.org/wiki/Mobile/Newsletter  -- it is currently a
 bit outdated since it has been around for a while. Given the comments on
 phab ticket.  https://phabricator.wikimedia.org/T93529, it is likely that
 this needs to be streamlined with other newsletters, however, meanwhile the
 coordination, please check and let me know:
 1. What would be the best approach to create it --agree on sections (new
 features, testing, etc) where volunteers, PMs and CL add details to?
 2. This format is too detailed? Too brief?  What else do we need to see on
 a newsletter for mobile?

 Obviously, it has to be made mobile friendly, as well. :)

 Comments, suggestions, thoughts?

 Many Thanks!
 Moushira

 ___
 Mobile-l mailing list
 mobil...@lists.wikimedia.org
 https://lists.wikimedia.org/mailman/listinfo/mobile-l


___
Wikitech-ambassadors mailing list
Wikitech-ambassadors@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-ambassadors

Re: [Wikitech-ambassadors] Huge change in the API documentation

[Amir E. Aharoni]

It should be mentioned in one sentence in the newsletter, even if it has
little influence on most readers and editors. It does have rather major
influence on translators, however.
בתאריך 3 בנוב 2014 21:07, James Forrester jforres...@wikimedia.org כתב:

 On 3 November 2014 10:10, Jan Ainali jan.ain...@wikimedia.se wrote:

 Recently there was a huge change in the API documentation at /w/api.php

 I found a notice here:
 https://lists.wikimedia.org/pipermail/mediawiki-api-announce/2014-October/71.html

 Should this perhaps go into the tech newsletter (I couldn't find it in
 the last five)?


 ​I'm not sure it's of much interest​ to many people reading this list –
 especially as the i18n progress for the APIs is still so early that they
 aren't going to be as well translated as users should expect. Perhaps we
 could do it as a by the way note?

 ​J.
 --
 James D. Forrester
 Product Manager, Editing
 Wikimedia Foundation, Inc.

 jforres...@wikimedia.org | @jdforrester

 ___
 Wikitech-ambassadors mailing list
 Wikitech-ambassadors@lists.wikimedia.org
 https://lists.wikimedia.org/mailman/listinfo/wikitech-ambassadors


___
Wikitech-ambassadors mailing list
Wikitech-ambassadors@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-ambassadors

Re: [Wikitech-ambassadors] wikis using badges

[Amir E. Aharoni]

As Matanya said, hewiki is missing and it uses the FA class in Vector.css

And this list should really really be in a wiki page somewhere.


--
Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי
http://aharoni.wordpress.com
‪“We're living in pieces,
I want to live in peace.” – T. Moore‬


2014-07-17 17:43 GMT+03:00 Lydia Pintscher lydia.pintsc...@wikimedia.de:

 Hey :)

 Wikidata will soon be able to also maintain article badges like good
 article and featured article. To configure this properly we need a
 list of all wikis that are already supported by Wikidata (Wikipedia,
 Wikivoyage, Wikimedia Commons, Wikisource, Wikiquote) and use badges.
 If your wiki does use badges, has Wikidata support and is not in the
 list below please let me know.
 Thank you for your help!


 Cheers
 Lydia


 kmwiki  Common.js
 huwikibooks Monobook.js
 nsowiki Common.js
 huwiki  Vector.js
 huwiki  Modern.js
 afwikibooks Common.js
 pswiki  Common.js
 dsbwiki Common.js
 bswiktionaryMonobook.js
 urwiktionaryCommon.js
 kshwiki Common.js
 kshwiki Common.css
 liwiki  Common.js
 iswiki  Common.js
 iswiki  Common.css
 bawiki  Common.js
 bawiki  Monobook.js
 anwiki  Common.js
 quwiki  Monobook.js
 cawiki  Common.js
 vowiki  Common.js
 cywikibooks Monobook.js
 mtwiki  Common.js
 nnwiki  Monobook.js
 nnwiki  Common.js
 fiwiki  Common.js
 fawikiquote Common.js
 cuwiki  Common.js
 iswikibooks Common.js
 ltwiktionaryCommon.js
 srwikiquote Monobook.js
 ruwiki  Common.js
 fawiki  Common.js
 pdcwiki Common.css
 pdcwiki Common.js
 bswiki  Common.js
 fowiki  Common.js
 myvwiki Common.js
 hrwikiquote Monobook.js
 tpiwiki Common.js
 ltwiki  Common.js
 ltwiki  Common.css
 ltwiki  Modern.js
 mlwikiquote Common.js
 bgwiki  Common.js
 idwiki  Common.js
 fawikinews  Common.js
 ttwiki  Common.js
 plwiki  Gadget-featured-articles-links.js
 bswikiquote Monobook.js
 uzwiki  Common.js
 kawiki  Common.js
 srwiktionaryMonobook.js
 jvwiki  Monobook.js
 jvwiki  Common.js
 gvwiki  Common.js
 arwiktionaryCommon.js
 nlwiki  Common.js
 cywiktionaryMonobook.js
 biwiki  Common.js
 ilowiki Common.js
 hewikivoyageCommon.js
 cewiki  Common.js
 scowiki Common.js
 miwiki  Monobook.js
 kaawiki Common.js
 cawikinews  Monobook.js
 pflwiki Common.js
 pflwiki Common.css
 gdwiki  Common.js
 gdwiki  Monobook.css
 gdwiki  Common.css
 mkwiki  Common.js
 rowiki  Common.js
 elwiki  Common.js
 sqwikiquote Common.js
 guwiki  Common.js
 tgwiki  Common.js
 cswiki  Common.js
 svwikiversity   Common.js
 skwiki  Common.js
 newiktionaryCommon.js
 zhwiktionaryMonobook.js
 kwwiki  Monobook.js
 kawikiquote Common.js
 ptwikiquote Common2.js
 afwiki  Common.js
 afwiki  Common.css
 udmwiki Common.js
 gawiktionaryCommon.js
 mswiki  Common.js
 thwiki  Common.js
 sowiki  Common.js
 newiki  Common.js
 lbwiki  Monobook.js
 lbwiki  Common.js
 hifwiki Monobook.js
 dawiki  Common.js
 liwiktionaryCommon.js
 etwiki  Common.js
 gawiki  Common.js
 viwiki  Common.js
 ttwikibooks Common.js
 eswikivoyageCommon.js
 euwiki  Common.js
 euwiki  Monobook.js
 kawikibooks Common.js
 nowikiquote Monobook.js
 bswikisourceMonobook.js
 mlwiktionaryCommon.js
 mrjwiki Common.js
 alswiki If-history.js
 alswiki Common.css
 alswiki Common.js
 bnwiktionaryCommon.js
 trwiktionaryCommon.css
 azwikiquote Common.js
 tewiktionaryCommon.js
 minwiki Common.js
 azwiki  Common.js
 jawiki  Common.css
 jawiki  Common.js
 jawiki  Vector.css
 kbdwiki Common.js
 tawiki  Common.js
 warwiki Common.js
 iowiki  Common.js
 mrwiktionaryCommon.js
 zhwiki  Common.js
 abwiki  Common.js
 sqwiki  Common.js
 bat_smgwiki Common.js
 mlwikisource

Re: [Wikitech-ambassadors] Deployment highlights for the week of August 26th

[Amir E. Aharoni]

2013/8/24 Greg Grossmeier g...@wikimedia.org:
 == Thursday ==
 * MediaWiki 1.22wmf14 will be rolled out to all Wikipedias.

 * CodeEditor support will be enabled for all JS and CSS on all wikis

I committed a fix to an issue that would affect JS and CSS editing in
right-to-left wikis:
https://gerrit.wikimedia.org/r/#/c/80707/
https://gerrit.wikimedia.org/r/#/c/80708/

It would be very nice to get it reviewed, merged and deployed along
with the change that enables CodeEditor for all JS and CSS.

--
Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי
http://aharoni.wordpress.com
‪“We're living in pieces,
I want to live in peace.” – T. Moore‬

___
Wikitech-ambassadors mailing list
Wikitech-ambassadors@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-ambassadors

Re: [Wikitech-ambassadors] jQuery 1.9 will remove $.browser (deprecated since jQuery 1.3 - January 2009)

[Amir E. Aharoni]

Thanks a lot for the notification, and for doing it on wikitech-ambassadors.

It's used in a bunch of gadgets in he.wikipedia. We'll fix it.

--
Amir

2012/11/7 Krinkle krinklem...@gmail.com

 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


 ___
 Wikitech-ambassadors mailing list
 Wikitech-ambassadors@lists.wikimedia.org
 https://lists.wikimedia.org/mailman/listinfo/wikitech-ambassadors

___
Wikitech-ambassadors mailing list
Wikitech-ambassadors@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-ambassadors