Fixed, thanks :)

We're picking the list from a portal and it takes about 7 days for migrated
tools to stop showing up there.

Already done I think, thanks

Already done I think, @komla I went doing so for some of my tools, can you update the list your are creating these from? Thanks 🙏

Took care of it I think, thanks :)

So it turned out non-modal OOUI doesn't have any of CSSs modal one has to make a correct dialog anyway,

This functionality isn't actually enabled on Wikimedia sites:

Experiencing the same issue, possibly is broken since https://github.com/wikimedia/mediawiki-extensions-FeaturedFeeds/commit/3ee517cb and T255380?

Line numbers are in the left side while editing CSS/JS codes, I think a consistent behavior is expected here.

Sure! Done

Nice bug report! Can repro here in Firefox also so isn't Chrome specific.

Yep. Thanks

Fix will be in Chrome 78

@Aklapper, no relevant in 2019 as far as can be seen, feel free to CC me to other Chrome 76 related ones though.

Filed as https://bugs.chromium.org/p/chromium/issues/detail?id=1010669

Filed as https://bugs.chromium.org/p/chromium/issues/detail?id=1010654

Generally speaking, Chrome 76 seems to be rather buggy for us

Filed as https://crbug.com/1010641 with a minimal reduction

Chrome and is in Incognito mode as can be seen in the screenshot, repros with safemode=1 also

My new tiny tool based on react (didn't go rewrite my old ones yet), https://fa.wikipedia.org/wiki/%D9%85%D8%AF%DB%8C%D8%A7%D9%88%DB%8C%DA%A9%DB%8C:Massblock.js having jsx around could be huge boost, still, is nice to have react around.

Going back to old fashion diff sharing, I am still not sure where to put urlencode and which one should I use, I only know this can work and I am OK if someone else also want to fix the issue but please fix ASAP now that it hits lot of users. Thanks

@Aklapper: Thanks for the link. I believe it has not the best UX but well I see the reason, so.

Apparently Gerrit is down right now https://www.isitdownrightnow.com/gerrit.wikimedia.org.html

Apparently I don't have the right to mark as duplicate.

Ladsgroup, you were also unable to see the issue? I see it on EVERY section edit in Persian Wikipedia regardless of being logged in or not and one should be able to see it on editing https://test.wikipedia.org/w/index.php?title=Talk:%F0%9F%98%83&action=edit&section=1 or using this

I've uploaded a possible fix for it here https://gerrit.wikimedia.org/r/496630 but here is someway to reproduce it reliably,

Now it makes sense. Thanks!

I used to have that also from time to time, I guess it will be nice if you could have a look at the logs of the page and when it is shown to the users, pretty sure you will find something interesting.

Ok. I experienced a bit with it and it looks fun so let me claim it :)

Just to note use of reversed words is ES5 not ES6 as https://stackoverflow.com/a/17911822 In ECMAScript, starting from ES5, reserved words may be used as object property names "in the buff". This means that they don't need to be "clothed" in quotes when defining object literals, and they can be dereferenced (for accessing, assigning, and deleting) on objects without having to use square bracket indexing notation.

Great, I was able to fix all the issues here https://fa.wikipedia.org/w/index.php?title=%D9%85%D8%AF%DB%8C%D8%A7%D9%88%DB%8C%DA%A9%DB%8C:Gadget-experimental-react.js&diff=25445722&oldid=25445607 the issue is jsmin raise error when using reserved keywords as property, like .delete .default .for and others. Please make that work also if possible. Thanks

I mean apparently line is "var hasSymbol = typeof Symbol === 'function' && Symbol.for;" which is weird. Sorry that I don't have a local installation of MediaWiki right now to check this better, I am trying to get jsminplus.php and run it independently to see whether I can improve it or fix the script issues.

Thank you Krinkle. I've converted hex numbers to decimals but I still see some issue. Ideally I want to apply such fixes locally for a while and being able to not care about those fixes on updating.

I can't see any ES6 specific syntax here https://fa.wikipedia.org/wiki/%D9%85%D8%AF%DB%8C%D8%A7%D9%88%DB%8C%DA%A9%DB%8C:Gadget-experimental-react.js can you recheck?

Thank you guys!

This disturbs RTL wikis, having infobox left aligned is not that expected on Persian Wikipedia, and its info shouldn't be left aligned in any RTL wiki. See

I was wrong, I think date conversion misled me.

@eranroz that is not syncing it to a version after 2017-07-02 but https://gerrit.wikimedia.org/r/380438 does.

Hey guys, is this discussed last week or will be on the next? Also have a look at the end of the linked discussion to see the already developed tool.

Thanks for always being around @Aklapper :) well, you can consider my comment as an excitement and encouragement for this work, would be nice if you guys could have a look at the help topic of the extension and point it on the documentation, as said such feature is needed for RTL wikis using help editor tools and such and many of that wikis need such capability that I don't see much on non-RTL ones.

Finally something on the right direction! Not another nonsense batshit (sorry for the language, of course just a personal opinion to stress this out) like "New wikitext mode", "VisualEditor", "ContentTranslation (cx)" editors, all of these attempts should've used something lightweight like this so they could gradually make newcomer users familiar with Wiki's syntax, just like what GitHub did with its markdown system. As an example, we have complains from confused people on my local Wiki that they couldn't figure out why the text they've entered can not pass abusefilter and other global/local site blacklist rules just because they can not the whole source on cx…

Any news around? This really delayed my work as some of the models I am going to use for the upcoming works (can be tracked on the given link) needs more system privilege...

Also not something that I would use immediately (as I am not going to do such training this soon, and even on that case, that computing intensive training) but it would be nice if you could consider provide some GPU capable machines between options you have for creating a new machine, for the future developments. I had some experience with them locally, both through pure CUDA and ML libraries and can use them already for my private uses. AWS, however, provides them as a service but I don't have access to it.

3.6 will be just fantastic for my use!

Great. It works there! And nice, an updated Python! Thank you very much!