They don't need tooltips at this point.

I updated it with "and". Sorry it was a typo in the design. So to reconfirm
we are dropping the week. Day, Month and Year stays. Have removed the row
counter too. Here's the updated design

I had a look at case 2 and based on the confusion in column header and value related to permanent items, will propose the following change.

@GMikesell-WMF please use this updated version of the design for validation. We discussed this in a planning meeting sometime ago.

Ah yes I overlooked it sorry. It should say

Yes it should change from singular to plural if multiple rows are selected. I think column name should be singular because it's the header of the cells that each contain only a single page title. Thanks for catching this!

✅ 🙏🏼

Looks good to me. Only one I am not sure about is Edit raw watchlist. But if it's an existing term and the users understand it, I have no say.

Remove sounds better.

Should this be a task for design systems?

@Samwilson it should be fine to begin with. Surprised that Codex doesn't support this. I thought growth team was the first to use this component.

Wasn't aware of it. Ok then let it be in its original position. We can close this ticket.

"Why was this implementation chosen?" sounds more natural. Alternately "Why did we chose this implementation?" could work too. If it's an external link, please use the Codex icon LinkExternal next to the link.

Added a design update in https://phabricator.wikimedia.org/T358807

In T358807#11415115, @DSmit-WMF wrote:

A proposal for this. Perhaps should be checked/improved by @gonyeahialam or @JSengupta-WMF

Cancel button should take the user to the whichever they invoked the submit a wish form from. If it's from a focus area page, it will go back to that focus area page. If it's from the overview page it will go back there and so on.

From the acceptance criteria, I understood that automatic vote of the wish author won't be displayed (assumption here: not counted = not displayed) till the wish is in vote-able status. So the default wording can still work.

@MusikAnimal thanks for taking a pass on it proactively. I have now updated the designs so please follow the button style and the user flow as per https://www.figma.com/design/JcTMFwbEJPpCKBiZ16Jkel/Future-of-the-Wishlist?node-id=3797-150914&t=Lv3TuFAAJWBHd1Lf-1.

Looks good to me!

Go with View 0 wishes in this area. I don’t see this situation arising
easily as the staff won’t create focus areas till they find a common theme
between wishes.

Thanks! Otherwise looks good.

Quoted Text "The "View N wishes in this area" link should jump to the "Voting" section of the focus area page"

Yes let's go with Community Wishlist/W123

Sounds good. Does unassigned translate well? We can also go with just a hyphen (-) I have shown an example of what you recommended, below. If this seems fine, I will update the published design.

Use these updated designs to triage this request
https://www.figma.com/design/3PthdmimQ8FiuhGIsLhmZi/Multiblock?node-id=3827-16431&t=6dK3Bo6uxvMgtwVm-1

The option marked "After" on the table looks great. If what you mentioned on the Slack about the importance of wish ID to certain volunteers, you can keep the same font size <h1> for the wish ID within parenthesis too.

If we decide to block voting before a wish is accepted by us, the message should say

FInal slides: https://docs.google.com/presentation/d/13TQY7HAC9dQEgx9OXX9-Mx_NE8oEjjXj/edit?slide=id.g3668fed620f_1_3446#slide=id.g3668fed620f_1_3446

Why would wishes under review not be eligible for voting? It is a good
signal for us to see how the community prioritizes wishes.

No further explorations are required at this stage for this task.

We can do both. Message when the tab is empty and in the tooltip when there are items in that tab already.

For 2. I would rather go with an error message whenever there is an internet issue notifying user about the main issue i.e. your internet connection is poor/no internet connection. What would be a valid (and quite widely used) use case for us to allow user to enter something that we don't know about?

Reusing the same icon for now is fine while the design team works on a new icon for favoriting templates. We are not rolling this feature out on App anytime soon. Will revisit it.

Yes I confirm it from the design side. It has been decided keeping in mind scalability in the future and the proposal came from the Editing team. So the first acceptance criteria needs to be updated in the description.

Sure let's do that.

Let's drop the icon in that case.

Thanks for creating this task! This was long due. Please feel free to contact Julieta and me for more context and history of diff. From engineering side, Harumi Monroy was the last person to work on this.

I matched the states with the Codex toggle button and the current colour scheme is fine.

Let's move the reload button to the left of the preview button. On toggle the reload button can disappear.

@HMonroy isn't it this one? https://www.figma.com/design/3PthdmimQ8FiuhGIsLhmZi/Multiblock?node-id=3827-16431&t=kbBWkI9xuKkZe3Wh-1

@HMonroy I removed the Blocks on link from Figma. https://www.figma.com/design/3PthdmimQ8FiuhGIsLhmZi/Multiblock?node-id=3827-15847&t=rPldWrTy6u63hDhf-1

Both sound good to me. @AAlhazwani-WMF wdyt about the padding that Sam asked earlier on March 14? Doesn't bother me either way but I'm generally not a fan of overrides unless necessary.

@kostajh here's the button on the UI if that's what you are asking for https://www.figma.com/design/3PthdmimQ8FiuhGIsLhmZi/Multiblock?node-id=3827-15847&t=4RbpgOPjM8PpF0eD-1

Copied over from the internal discussion. We can hide them when a table is empty. But when none of the tables are empty, on which table header would it show up?

I changed the button text to keep it simple. It will translate better to other languages too I feel

@TheresNoTime I'm still exploring the solution. The design you saw was just a placeholder. With the undo feature I am leaning towards the OOUI message style (2nd one)

Updated the description

Yep that's what I wrote in the original bug report, "Block updated" for edit scenario

Yes. Sorry I forgot to add it to this ticket.

This ticket is to log a design change from the user test. It's not a high priority task or a blocker that needs to go in the current release.

Date before time should be OK. Thanks!

Yes

@dmaza the type column can be where it is currently now. But "Change visibility" should be under action column like on the active block table. I have added an example of the block log table in Figma. Assuming the suppressed log table has the same parameters.

It's the default behavior on Codex accordion component. Did we override this in the current design?

Borders within the table should also be enabled. Should it be a seperate ticket?

This is a new parameter addition within an existing column. This parameter wasn't being shown earlier in block parameters.

It's all related to the form so I listed them on this ticket. Feel free to move around.

We will display Show IP under the target field and Contribs link on the table title next to the target name.

Pre user test designs had "Active block" followed by "Block form" followed by "Block log". We are moving up the block log. You predicted it correct and it was confirmed through the user test.