As discussed with the team, I have created a follow up ticket to treat the editor part (T410761) and will move this to Design Signoff

"Learn more" external link (only visible when description expanded)

@eamedina Can you please review AC5 if that's fine? Thanks!
Is "Start translation" fine or does it have to be "New Translation"

The link between gerrit and phab was missing, just added it for documenting purpose. Patch has been abandoned.

I have tested again and I'm not able to reproduce the issue, I suggest we close this one. In the Drive link below you can see my screencast, mind you this test comes a couple of years later and now the unified dashboard is a reality. Either way the desktop editor is still the same, and replicating the same steps does not generate the bug anymore.

I have tested on testwiki and this work meets all acceptance criteria as detailed below:

It no longer appears on the section screen, but when you go to editing, the HTML markup shows up in the title

Following further testing within the team, general feedback is time estimations are still a bit off and discouraging. Moving back for more fine-tuning

@SGautam_WMF has it been discussed already what we're gonna do about the 'Active filters' section? Currently it looks like this [1], the desired state in the description of this ticket doesn't show this section, should I remove it?

Hey George—

@GMikesell-WMF thanks for the QA, good catch finding a bug! The way it's intended to work (as specified in T360570) is that we only apply the 'quick translation' styling (green color, label) if it's estimated to be less than 15 minutes. I have submitted a patch for review that addresses your feedback

Thanks for the clarification Pau, this makes sense to me. Please see: https://imgur.com/a/U1l21hQ. I've updated the code so it satisfies the expectations to the best of my understanding. Note that selecting a language already represented in tab does not change the tab order, yet if the user selects it and returns to dashboard, then when coming to search view again the source language (previously selected) is presented at the first position. In other words, whenever the search view is displayed, it starts with current source language at the first position.

@Pginer-WMF surfacing from Gerrit a comment by Stephane:

A couple of other questions:

we have implemented tab specific search filter as Suggested by Pau in one of this comments, please confirm

Thank you both. This is how it's looking so far: https://imgur.com/a/vAZwVda [1]

Thanks Pau for the confirmation and Phabricator tips! Patch has been updated and images "attached"

Hey @SGautam_WMF I tried reproducing this error but was not able to. Can you please confirm if you're still able to replicate it? If so, let's try to think of other variables that could be playing here for other to reproduce.

@SGautam_WMF @Pginer-WMF —Patch has been approved but a question came up regarding the copy. What do you think would be the best copy for the different cases below?

@Pginer-WMF given that this seems to be triggered from names running out of space, would the preferred solution in this case be to use an ellipsis similar to how you described in T385884#10737936?

Thanks Stephane, indeed it's stated as such in the documentation. I believe even without the weighted_tags perspective we still have enough for T391230. If we all agree this is the case, we can move this ticket (T388942) to the next logical column

AC2: The first search result should be highlighted by default.

Before and after images below, please note this is for narrow desktop screens only. On mobile, the "New translation" button is not meant to be shown.