Note that dark contrast is looking low on mobile view for me on android + linux firefox in several places

Okay, I took a first pass at registering modules in extension.json; this is not the most important step in itself, but IMO it will make the other steps cleaner if we look at it first and then base future changes on this.

we'll verify on safari when it rolls out on the train

We should fix T421414: Active discussion module appears briefly before being hidden in PersonalDashboard before going loud on enwiki

just noting for my fellow moderator tools engineers that this is for the personal dashboard superset dashboard, not the personal dashboard logstash dashboard. We have more than one dashboard dashboard. We may need to list these out in a dashboard dashboard dashboard.

Sticking this in Reproducibility check column as a proxy for "investigate"

In T419158#11681074, @Samwalton9-WMF wrote:

Thanks for working on this. Just to clarify, what is the user-facing impact of this? How many deletions would need to be queued before a rate limit was hit? Is the limit per-user or project-wide?

A thought that might muddy the waters here; so far we've been talking about recent changes in terms of single edits, but maybe this is a case where we want to highlight a range of edits together? I'm thinking about rc/watchlist grouping and multi-rev diffs, etc. feels like a potential future thing.

In T130134#11750583, @A_smart_kitten wrote:

@jsn.sherman Understandable if ModTools doesn't plan to pick up the work; but, unless this is something that the team has explicitly decided shouldn't happen, should(n't) this task be left open in case someone else wants to submit a patch for it? /genq

I'm declining this task as we don't have any plans to pick up the work.

@Samwalton9-WMF I'm not sure who is supposed to do what here, so I'm sticking this in radar with the assumption that this is going to be an analytics request

@Samwilson I believe this is expected behavior rather than a bug. I can't recall how we landed at the current state, but I think changing this would be a feature request.

this is looking much better on testwiki, IMO:

the exception fix is rolling out on this week's train, and the multilingual enablement patch is in progress.

We had a backport lined up for this but gerrit was down for the majority of the window, so it's just going to have to wait.

Our Mobile preferences id selectors are creating a specificity war and @Volker_E has kindly offered up a patch that needs reviewing. This was either me or @Scardenasmolinar, so I'll have a look by EOD on 3/23

@Samwalton9-WMF could you have a look at this feature request to help determine if we should accept it?

noting that this looks like an emergent check user / mobile watchlist + rc issue; putting it in our queue

In T418613#11724927, @jsn.sherman wrote:

@BAPerdana-WMF just checking in; are you seeing / have you seen the blue dot and/or user menu link for the Personal Dashboard?

We talked in engineering about adding an attribute to log the source of the edit (eg. rc, watchlist, etc); this wouldn't show up in the superset dashboard, but could be queried after the fact with some effort.

Thanks for writing this up @CMyrick-WMF,

Thank you for tagging this task with good first task for Wikimedia newcomers!

verified on testwiki

verified on testwiki

In T414408#11669031, @Samwalton9-WMF wrote:

We should check that if the page doesn't exist locally, false positive reporting page links (in contribs/history) are still generated correctly and without error.

@BAPerdana-WMF just checking in; are you seeing / have you seen the blue dot and/or user menu link for the Personal Dashboard?

verified on testwiki

verified on testwiki

verified working on test wiki:

In T419835#11721389, @Scardenasmolinar wrote:

I have tested this patch locally and found that validation is broken in several fields:

1. You can enable both models (multilingual and language-agnostic) without throwing errors:

2. You can add non-numeric values to the multilingual threshold and numeric values lower than 0.850:

3. You can add user rights that do not exist and add non-numeric values to user reverts per page:

update: the patch for this is turning out bigger than I'd initially hoped; work is proceeding and I do anticipate getting a fix backported this week.

@Arendpieter thanks for picking this up! I've put it in our review queue.

I had to set this down to deal with other release tasks. I'll pick this back up tomorrow. The TL;DR is that AutoModerator was created before CC was quite done and has it's own configuration wikipage config routing and validation. I believe this is the source of the circular dependency. I'm well along the path of ripping out all of the obsolete code. I still need to finish updating the validator and tests. We should then be good to go.

note that, for reasons, we can't actually set the survey url per-wiki, we have to set it to the same value across all wikis, which is what I will do.

noting that I previously thought about moving error messages out of this component and into a mw toast (or some other ephemeral ui element); this could be a good opportunity to move all of the error/warning ui into the loading state component

yes, this is all the same issue; I'm confident that the problem is with AutoModerator and that we can resolve it today

In T417809#11676320, @Mcljlm wrote:

What do you mean by namespaces?