Thu, Feb 14
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
Wed, Feb 13
Tue, Feb 12
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.
Mon, Feb 11
For the validation of the specific tags, we need to look into allowing for validation in the original ooui widget. I created T215760: TagMultiselectWidget: Add validation method rule for arbitrary tags to look into this in OOUI.
Sat, Feb 9
This resolves "The 'Pages' input field should not suggest Special pages" and retains the "The error messages should continue to appear if the admin somehow manages to get these through"
Fri, Feb 8
Okay, so I think that it might be a good idea to slightly rename things, and potentially get a bit of consistency with the events.
Thu, Feb 7
- Add deprecation note to release notes
Okay, so I had more time to actually delve into the way the code works, and I'm slightly amending my analysis. The problem with the gadgets isn't really how to filter through the itemMatcher, which only works if the entire set of items already exists -- the problem with the specific SearchWidget is the API call. We need to make it possible for those gadgets to adjust the query that's sent to the search API.
Wed, Feb 6
In reference to Joe's question --
Tue, Feb 5
Wed, Jan 23
@MusikAnimal, I understand you want to delve into this one with teh data we already have -- I think that's a good idea, even to start flushing out any challenges we haven't yet seen with the current data.
This is great. @MusikAnimal question -- for old events, do we want to create a check that redoes this ? So, if we kept fetching PageIDs for events that ended up until now, we might have, in the DB, extra PageIDs that are redundant and unnecassary for that event. Do we want to add a small check that if / when people update older events, we make sure the info in the PageIDs only contains the pages that are in the range?
Tue, Jan 22
That looks good and straight forward to me, we can has out any further details if needed during estimation.
Sun, Jan 20
This is actually a really interesting idea, and could answer a lot of usability with automated stuff or quick loading of mediawiki when needed.
Jan 18 2019
Jan 16 2019
You're right, I think I connected the tasks wrong. Thanks for fixing it!
Jan 15 2019
@MusikAnimal this is merged but is this in production? Was it deployed? If so, we can move the ticket to QA/Product.
@jmatazzoni is there a similar task to this ? I feel like I just wrote something about this...
If you look at Special:Search (open the "Advanced Search" drop down) in Edge, the help icons do show up, but the rules look to be exactly the same, which is really confusing -- why does it work there but not in TemplateWizard?
Yeah I just verified on my Windows PC in Edge 17; the problem isn't visible on https://doc.wikimedia.org/oojs-ui/master/demos/ but is visible in MediaWiki while using the TemplateWizard dialog.
Does this appear in the OOUI demo page too? This sounds like an OOUI bug.
Jan 14 2019
Jan 12 2019
Actually, I'm not sure, but isn't the "official" definition is different between wikis? It might be that we are defining something specific for Event Metric's purposes rather than going with the (inconsistent, if I remember right?) definition of the different wikis?
If you add it to the first, it'll get lost if you scroll?
Jan 11 2019
Jan 10 2019
Clarification (we can do either) -- Do you want the popup to only be shown once and then never again, or to be shown until the user purposefully clicks "ok/dismiss"?
Jan 9 2019
Jan 4 2019
I saw the WIP PR with Leaflet demo'ed on @Samwilson's computer. It's awesome, works amazingly well seemingly out of the box, and covers a bunch of those zoom/pinch/move features. We could probably share screenshots, but it basically looks like you'd expect; the image and the +/- buttons, enabling zoom and movement in desktop and mobile natively.
Jan 1 2019
This was done during the hackathon, and then cleaned up a bit.
Dec 21 2018
Dec 20 2018
Dec 19 2018
Notes from the Engineering discussion:
The fact this is an error doesn't make much sense here, since this is a common behavior that is expected. You reach the "edge" of a result set (either the end or the beginning) not as an error, but as a state.
Dec 18 2018
Dec 15 2018
Dec 13 2018
Dec 11 2018
Nov 30 2018
Nov 29 2018
Yes, this is done. We're continuously adding some methods to the API, but we should create new tickets as they come.
Nov 27 2018
For reference, PR is here: https://github.com/wikimedia/svgtranslate/pull/20
Nov 26 2018
This is a future enhancement for sure, not really something we should deal with for the MVP.
@Samwilson I tried to merge the patch (looks good) but it fails: