.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 b
irefox or Opera) and look at the console. Look for any
uncaught exceptions, deprecation notices or other messages and try to address
them soon (or report it to the maintainers of the gadgets triggering them).
-- Krinkle
[1]
https://doc.wikimedia.org/mediawiki-core/master/js/#!/api/mw.log-method-depr
tps://gerrit.wikimedia.org/r/#/c/137168/
[5] https://lists.wikimedia.org/mailman/listinfo/wikitech-ambassadors
-- Krinkle
PS: You can get a sense of the progress on our different migrations, past and
present, via these graphs: http://codepen.io/Krinkle/full/zyodJ/
__
Hey all,
On 3 Jun 2014, Krinkle wrote:
> TL;DR:
> * We did not make the breaking change last week for Wikimedia; it is
> postponed.
> * MediaWiki 1.24.0 will ship with jQuery Migrate switched off.
> * Wikimedia & non-Wikimedia wikis can enable jQuery Migrate if needed.
>
7;t show it because the diff change content is
bolded.
Filed as https://phabricator.wikimedia.org/T101219
<https://phabricator.wikimedia.org/T101219>.
— Krinkle
> On 24 May 2015, at 23:21, Nemo wrote:
>
> On 15 April 2015 at 13:54, Ricordisamoa <mailto:ricordisa...@ope
ia.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.
Fixed, and deployed.
Thanks for reporting and sorry for not noticing that earlier.
— Krinkle
> On 5 Aug 2015, at 17:12, Max Semenik wrote:
>
> Already reported as https://phabricator.wikimedia.org/T108139
> <https://phabricator.wikimedia.org/T108139>
>
> On Wed
> On 7 Aug 2015, at 13:05, S Page wrote:
>
> On Thu, 06 Aug 2015 01:24:03 +0200, Krinkle <mailto:krinklem...@gmail.com>> wrote:
>
> TL:DR; Double-check your wiki's site scripts and your personal scripts
> to ensure "document.write" is no longer used
around May 2016).
Tech News will announce this change as well, but please help carry this
message into your communities. In January, we will send a reminder before
the change happens.
Yours,
-- Krinkle
For details about the JavaScript-less experience, see
https://www.mediawiki.org/wiki/Compatibility
fix missing dependencies on wikibits. In
MediaWiki 1.28, to be released in November 2016, the wikibits module will
be removed entirely.
-- Krinkle
[1] https://www.mediawiki.org/wiki/ResourceLoader/Legacy_JavaScript
[2]
https://lists.wikimedia.org/pipermail/wikitech-l/2013-October/072776.html
[3
see:
https://www.mediawiki.org/wiki/ResourceLoader/Core_modules
Yours,
-- Krinkle
Phabricator Task: https://phabricator.wikimedia.org/T122755
[1] wikitech-l: First round of JavaScript deprecations (introducing
mw.log.deprecate for wikibits) - MediaWiki 1.23 (2013)
https://www.mail-archive
MediaWiki 1.30, inclusion of jQuery Migrate will made
configurable so that sites
that have already migrated may disable the plugin for better run-time
performance.
Track progress at <https://phabricator.wikimedia.org/T124742>.
-- Krinkle
[1] https://www.mediawiki.org/wiki/Beta_Cluster
[2] https://w
Hi Johan,
I want to thank you for the great work on Tech News. In particular with
regards shoving short description sentences for each feature that is
affected, and use of simple language. This is an underestimated talent and
it’s very important here.
Are there others routinely involved with this
On Tue, Jun 26, 2018 at 2:15 PM, Krinkle wrote:
> Hi Johan,
>
> I want to thank you for the great work on Tech News. In particular with
> regards shoving short description sentences [..]
>
This was meant to be "with regards __to having__ short description sentence
[..]&quo
Everyone on Wikimedia wikis will shortly be logged out and will have to log
back in again.
The protections we deployed on June 26 failed to cover some cases.
We have updated the traffic layer today to also protect against these cases.
-- Timo Tijhof
On Fri, Jun 26, 2020 at 3:44 AM Tim Starling
I've fixed the timestamp link to be this year instead of last year
(1624975200), and updated the various timezones.
My edit is awaiting translation approval.
-- Timo
On Fri, Jun 18, 2021 at 11:30 AM Dhaval S. Vyas wrote:
> Ignore that as I was referring to the below message on translate wiki,
TLDR: If you use "hard refresh" in your browser after editing a CSS or JS
page on the wiki, I'd like to hear about it so as to figure out whether
there may be a bug in the software. Please do test and confirm it for
yourself once more without a hard refresh, as it might just be an old habit
acting
17 matches
Mail list logo
