Fri, Apr 12
Merged. Should be in staging in a few minutes.
Thu, Apr 11
Tue, Apr 9
When did we introduce this? If we introduced it in a previous (and published) release, we might need to deprecate for the upcoming one? ... But if it's in between releases it's probably fine.
Wed, Apr 3
Tue, Apr 2
This is the quite entangled view of the "Enhanced" recent changes table. The structure is tabular, but this specific cell has several notations in it (like "N" for new page, etc) and in order to align them across the different entries, the line is either with the symbol, or with a space.
Mon, Apr 1
Sun, Mar 31
Sat, Mar 30
Fri, Mar 29
Just note that browsers started considering these custom messages as security breach. They allow us to display a warning before navigating away, but not to set the text of that warning.
Wed, Mar 27
Tue, Mar 26
I also think that making sure MediaWiki is installable and usable in shared hosting is a worthy goal, and there are definitely some instances where we should be more mindful of it.
Mon, Mar 25
Mar 21 2019
Mar 15 2019
Mar 14 2019
Mar 13 2019
What are the benefits that you see with this approach?
Mar 9 2019
Mar 8 2019
Mar 6 2019
I had a temporary issue with the dev asset build but it seemed to have been fixed. The original idea here is to make it possible to debug in staging and production. If we can do that easily with source maps, we can put those in both staging and production.
So, I'm a bit meh about this; first, I don't like using bits and pieces from different libraries, but that's a minor point. The second slightly more important point is taht if we're serious in allowing users to change their interface language, then some RTL languages have a flipped question mark, which OOUI is supposed to know how to deal with, but FontAwesome doesn't.
Mar 5 2019
Isn't there a flag on the user?
Mar 4 2019
Clarification: Excluding bots, in this ticket, means excluding edits that have the bot flag on them.
Mar 2 2019
@jmatazzoni so, we want to not count edits that were done on items that were created during the event. Is that right?
Mar 1 2019
Feb 28 2019
My suggestion is to drop logged actions completely. As far as I know and as far as I've seen, logged actions are indexed by the performer, not by the user that the action was made to which means that even the action of collecting this data will be risky performance wise, and will increase the level of complexity to consider async delivery and then storage/delivery of files, etc.
Feb 22 2019
Just a note, the ViewModel could use the mixin OO.ui.mixin.GroupWidget; the individual input widgets could then be infused and then immediately added through addItems and then we can do this.aggregate( 'change', this.whateverListensToAnyInputChange.bind( this ) to listen to any change event.
Feb 21 2019
I guess that's true, but the benefit of doing my approach is that we're setting up an API for it, which exposes the ability to do what you're suggesting.
Feb 20 2019
Feb 14 2019
Quick clarification (just to save implementation/confusion time in finding the code in the different parent widgets) :
This should be fixed by overriding doInputBackspace from TagMultiselectWidget in MenuTagMultiselectWidget
Feb 13 2019
Feb 12 2019
I don't know enough about the 'map' parameter to consider any behaviors that are needed or any edge cases to say how difficult it is to implement.