In sprint demo we noticed that the warning is not working for titles that have a space in the name. Example

In T350406#9343786, @WMDE-Fisch wrote:

@lilients_WMDE For Two-Column-Edit-Conflict-Merge it might be better to use Share of successful resolutions coming from TwoColConflict it seems to be more likely to show if something's wrong.

/me wags eyebrows towards Superset. The very big advantage of using that platform is that we don't need to write a separate aggregation layer to get the data into Graphite, we can query hive and mysql directly.

I just found this open feature request for the codex library: T350769: [S] Implement inline progress bar when submitting form. It could be an alternative approach to the implemented progress bar.

Stalled because of https://phabricator.wikimedia.org/T345261#9144316

Maybe the transition in these patches (moving some of the functionality to core) might be related?

Although the documentation shows a nice overlay effect for the progress bar, there does not seem to be a built-in mechanism to display the progress bar with an overlay effect. Or did we somehow miss it? If not, maybe it could be added? Not sure where to put these questions ... [Update: I added a ticket to the codex dashboard: T350805: Include overlay in progress bar component]

Agreed, that is actually strange. I also did not find any examples in the codex specification where there is an input field with a button next to it (neither in the TextInput nor in the Field ). Maybe we can ask someone from the design team, if we missed something or if the docu could be improved?

We tested the mobile view on en wiki and found a strange behaviour. Turns out that the advanced search field only shows for some screen sizes. There is already a ticket: T308845: Search form hidden on MinervaNeue on wide screens. But when the advanced search field is displayed the described issue does not appear anymore (see screenshot below). So we can close this ticket.

We decided against the close button because that would need some designing.
We tried the toggle button approach and it looked and felt weird.
We ended up with the suggestion in the ticket description: hide the diff view when editing. :)