El T410614#11429496, @ppelberg escribió:

Meta: "opening" this task as closing it depends on us making (and documenting) the following decisions...

What (if any) UX adjustments are needed before broader rollout/experimentation?

I conducted the test with different types of experience level users and the different button's copy variants, and here are the findings and next steps (see more details in the findings and insights doc):

Finally moved the border-colo-base fix to this separate task T409100: Review VE's OOUI components against Codex design guidelines. So we can solve this task.

El T403971#11404566, @Esanders escribió:

border-color-subtle, along with the small OOUI drop shadow, is the same as used by the toolbar and the mobile context, which this component mimics:

If we want to change that, we should file a separate task and make sure everything is consistent (e.g. external borders vs internal borders)

This task still needs to be reviewed. Sharing how it currently works (Google Chrome in Android device).

Status: I conducted a first round of tests. After conversations with @ppelberg, we decided to run a second round of tests.

El T403971#11399451, @EAkinloose escribió:

For "Revise Tone?", the border on top and below has @border-color-subtle; as opposed to @border-color-base. Does this need more work?

Following the work @Samwilson and I have been doing during the Wishathon 2025, I’m sharing the explorations and WIP implementation so we can keep iterating (also shared in the task's description):

El T368423#11389083, @Cparle escribió:

I meant inside the select - so like this

The text inside that box is a Codex msg, so if I change it then it changes everywhere there is pagination in Codex. I think it probably should change, because "rows" doesn't really make much sense

@Esanders I've updated the task description including all the design details to implement the proposal. And this is the Figma file in case you need to inspect them.

El T368423#11389025, @Cparle escribió:

In T368423#11389014, @bmartinezcalvo wrote:

Either "results" or "items" could work, but in order to be aligned with the Table's pagination, the "results" word should be included within the Select, not outside.

Ok ... so is it ok to change the message to "X results" for all codex table pagination everywhere? Or maybe "X results per page"?

El T368423#11388914, @Cparle escribió:

Actually now I think of it - we also don't know where we are in the resultset (we kinda do for search, but it's hacky), so we can't even say "Showing results 250-300 of many"

El T368423#11388992, @Cparle escribió:

@bmartinezcalvo I see that in the dropdown for results per page you have "X results" rather than "X rows" which is what's in Codex right now. I think that makes sense (or maybe something like this image below)

... but maybe better still would be to use "X results per page" in each item in the dropdown instead? I think that's clearer than "rows"

El T368423#11387936, @Cparle escribió:

@bmartinezcalvo right now we don't display "Showing results 1–10 of 999,999" and we can't commit to doing this in general - for search we retrieve a maximum of 10k results, and for database queries they're structured (for efficiency) in such a way that it's not possible to know the size of the resultset the user is paging through

Summarizing here the explorations and next steps discussed with the team: