Sun, Jan 21
Well, for one, it allows much more than even Lua to an average editor. I am not, however, a supporter of some ability to watch an article and get all CSS edits from it* (although ‘watch a template and get styles.css too automatically’ could be useful and probably will prove to be a must-have), but we need to get away from the false attitude of ‘CSS can’t be used in very bad ways and community can always enforce against the bad stuff’ either.
Tue, Jan 16
Is it not working again? The feed stopped at my end (in Discord bot that I am running) somewhere from 7:10 UTC and, given the history, I thought I’d ask if this is the case of failures again.
Sun, Jan 14
Tue, Dec 26
I would ask Editing team to look into this better: it is a very frequent bug appearing for anonymous editors in Russian Wikipedia. We have more than 7,000 stabilised articles (mainly the featured and good articles) and in each of those there were two different links on the stable version that is shown to anonymous viewers: VE link to old (stable) version and default editor link to last version. VE link should not differ from the link that is shown for default editor, and we even submitted a local fix for that (I suggest doing the same to other projects before it could be fixed) given how frequent this leads to deletion of edits due to not noticing that they edit the stable version and not the last version. Before VE was introduced, there were no such issues, so I am considering this a quite big regression.
Dec 19 2017
Dec 15 2017
Dec 12 2017
Follow-up from https://meta.wikimedia.org/wiki/Tech#Module:
Nov 23 2017
You got it wrong, it’s not a bug that is described in T180138, it is a different bug within the Timeless skin. For example, it works just fine in Vector, albeit with bigger paddings around the field.
Nov 22 2017
I was avoiding this conversation up until now, but I am going to respond as much as I can to this outrageous decision-making process that happened right here. First, you have enabled the skin on some projects to ‘test the waters’. Now, that modest support for testing the skin is presented as the same thing as enabling it as a permanent option in settings for all Wikimedia projects? I mean, seriously? About what consensus are you exactly talking about? There was consensus for testing stuff, there is, there was, there was never sought no consensus for indefinite (as it seems) enabling of this skin anywhere.
Nov 21 2017
I really don’t see how having enough technical debt already justifies adding it. There is literally no ability to turn off a skin from a Wikimedia project, so local technicians end up supporting Modern for those three people using it and now will be expected to support Timeless for those five people that would experiment with it.
Nov 20 2017
Nov 10 2017
Nov 6 2017
Nov 5 2017
Will there be a community discussion in which members of Wikimedia movement can express their direct opposition to such move?
Oct 25 2017
Sorry for taking so long to answer. Have no preference about bullet/full stop, bullet is probably more ‘language-resistant’ since there are other types of full stops in other writing systems.
Oct 21 2017
I feel like the most appropriate model to use is not to restrict usage of TemplateStyles pages anywhere (since there would be, for example, cases of testing the template code in your personal space), but to restrict the creation and editing of such pages to template/interface editors or sysop level.
Of course it could be added, but this is not the right option to pick and the localisation for Wikimedia portals, as far as I am aware, is updated every month or so (see T142582), and I believe that this change could be made much quicker than this.
Oct 19 2017
I can only speak for myself in this, but unless the 2017WTE will be as fast as the current editor from the get-go, I see no local developers taking interest in supporting this project in its current state. It should be quite easy to implement this support, at least seeing the similar work (with different premise) from German user Schnark , but until there is an ability for developers to use 2017WTE comfortably, I don’t see any support coming out of this. For anyone that is interested in doing this, however, veAutocorrect is pretty similar in its function and structure to wikificator (or wikifier); the only difference is that wikificator is supposed to be activated by user instead of doing everything in sync.
Fixing this, one must also consider that not all pages have the subtitle, so ‘Information for Falcon’ , for example, should not have any additional margin, like it was before this change was made.
Sep 30 2017
Aug 23 2017
Aug 21 2017
Was feedback from WMF Design team on this topic (T158012) met and resolved? I get the urge of the volunteers to develop something that is more modern-looking than the current skin, but I think it is fair to say that in the terms of design this new skin is lacking, to say the least. The choice of colours is completely groundless, skin does not use current conventions on typography (WMUI style guide or typographic refresh) and generally looks like a regression even from Vector.
Jul 24 2017
This is honestly good − there are some gadgets for Special:Delete that would completely break if it was turned into a custom <select>. It is the only reason the script for people deleting pages in Russian Wikipedia (https://ru.wikipedia.org/wiki/MediaWiki:Deletepage.js) still works, for example. (Padding is still a problem, yes.)
Jul 18 2017
Well, it still is not part of the same task since IIRC Monobook uses a different theme for UI elements (Apex) and it is not fully compatible with OOUI. The reasonable thing to do is to drop Apex theme in favour of OOUI for all skins, but it probably requires global changes that go beyond the scale of this particular improvement (and this task).
Jul 10 2017
Jul 6 2017
Reopening this per suggestion from @Nemo_bis. The fact that it is more prominent for newcomers does not justify the fact that red quiet buttons right now looks as red links in the interface, which is deeply unacceptable, especially there also can be a literal link for "Editing help" right besides it. And with it definitely looks as one of the links is non-existent, which is not an intended effect.
Another annoying regression after converting to OOjs UI: selected suggestions for ‘Preview page with this template/module’ can’t be autocompleted by going through the list, although in previous version this worked absolutely fine. Maybe we can at least disable it for TemplateSandbox gadget until this is fully resolved?
Jul 5 2017
Right of the bat: red "Cancel" draws too much attention, OOjs UI really should’ve not change the default behaviour of quiet buttons (mw-ui-quiet) from original MediaWiki UI where they were blue/green/red only on hover. I think this is a very major flaw of new design. It was not noticeable when this feature was available only via URL parameter, but it is more prominent issue now.
Jun 22 2017
If you want to try an experiment, you could, for example, change the default message, provide a gadget which does basically mw.config.set('mw.msg.wikieditor', '--~~\~~'); (this should change signature button in WikiEditor, don’t know about VE) and announce this change on your community forum to see how many people would revert to the old style (via Special:GadgetUsage after a month or two). We can try to get this experiment going on several wikis and get some feedback on this as a measure to test if this will be noticeable by users at large.
If there is no Special:Preferences redesign task, there should be. Beta features look out of place at current page and OOUI already has all elements to redesign the page.
Jun 21 2017
Jun 19 2017
A small note: Russian Wikipedia already uses somewhat unified look to the current Popups extension. It is not as fancy as some of the mockups here are but, in my opinion, these mockups seem too big for this kind of feature. Page Previews seem not as prominent as future Citation Previews in comparison.
Jun 17 2017
+ tracking category.
May 16 2017
Feel free to answer although I am certain that would not change anything anywhere, not even in the future conduct.
May 15 2017
Two questions that need definitive answers:
- Based on what exactly was this decided?
- Why there were no community discussions happening beforehand?
May 7 2017
May 4 2017
https://ru.wikipedia.org/?oldid=85228054 − thumbnails can be seen here changing on the fly.
May 2 2017
With issues like this it would’ve been best to abstain in the future from any major releases and changes (besides bug fixes) on the week before the week when no changes can be deployed. Situation when there could be a major change that is wrong and can’t be fixed in an urgent way is just wrong by itself.
May 1 2017
Apr 29 2017
Could this be fixed earlier by any chance? This is basically turning off the most efficient way of reviewing process (active users checking their watchlist), it is hurtful for the whole projects not to have these links and notices even in 1 day, not even talking about 10.
Apr 13 2017
It looks worse than I expected it to (because it is still ≈80% of needed width or height in comparison) but I don’t want to take your time anymore with such low-priority task.
Apr 12 2017
Apr 9 2017
Should’ve looked into it, seems to be same issue as T160749.
Apr 6 2017
Apr 5 2017
This version is fine, just to be sure − is white space on the right side necessary? Either way a lot better than now.
Apr 3 2017
Yes, the same ERR_CONTENT_DECODING_FAILED even with disabled cache (via Devtools) at https://ru.wikipedia.org/wiki/Шаблон:Медаль_Партизану_Отечественной_войны_1_степени
Another one to the pile: https://upload.wikimedia.org/wikipedia/commons/thumb/e/e7/Partizan-Medal-1-ribbon.png/40px-Partizan-Medal-1-ribbon.png (since there’s some manual fix available?)
https://upload.wikimedia.org/wikipedia/commons/thumb/f/f5/Flag_of_Cross_of_Burgundy.svg/23px-Flag_of_Cross_of_Burgundy.svg.png has the same exact problem. Other versions (1.5x and 2x ones) work fine.
Mar 24 2017
This is not the case, since there’s no hint about adding <br />, only <br>. <br /> isn’t in the source text either, but no hints etc. appear for it: https://i.imgur.com/LWiZFgk.png (sorry about not using file uploads).
Mar 23 2017
Mar 21 2017
No consensus from the local community here:
Mar 18 2017
Mar 14 2017
Mar 3 2017
Feb 25 2017
Feb 23 2017
Feb 19 2017
Feb 13 2017
Jan 22 2017
Jan 20 2017
Jan 8 2017
Dec 20 2016
Sep 3 2016
I object to proposed group name even after reading task you’ve linked to. This potential unification is maybe needed for autopatrolled etc., but it is rather harmful for entirely different groups with different purposes and rights. So, for example, if this group would be named ‘interface editor’ in other languages, it would just be an ambiguous name.