Hey @Prototyperspective, these sound like reasonable ideas for how to improve the user experience here, so I want to bring this to the attention of the Structured Data team (who are the official maintainers of this feature AFAIK). @AUgolnikova-WMF or @Sannita may be able to move this task to the appropriate place for triaging. I will say that I think the team's current focus is on improving UploadWizard, so this might not be an immediate priority.

Hi @Prototyperspective – are you familiar with Special:MediaSearch on commons? Here's an example of it in action:

So, the code to do this in the Dialog component is pretty trivial:

In T364777#9927956, @Jdlrobson wrote:

Can this be closed now?

In T368421#9922382, @AnneT wrote:

All that to say: let's consider carefully before making a change whether a change is really necessary.

In T367101#9905637, @DTorsani-WMF wrote:

@lwatson Per Eric's request to review and leave any design feedback on the latest demo, here are a couple pieces of feedback (which you might already still be working on).

• It looks like line-height is not being set on the text within the tooltip, so the tooltip is appearing much smaller than it should. The tooltip height should be a minimum of 24px tall if the line-height is ~20px and the vertical padding is 2px.

In T367101#9907524, @CCiufo-WMF wrote:

I'm a bit confused about this task's relationship to T366104: Tooltip: Introduce a WIP component to Codex. Should that task actually be resolved if this is a continuation of that work?

Tooltip should animate in using opacity and scale

• Opacity starts at 0 (opacity-transparent) and ends at 1 (opacity-base)
• Scale starts at 75% and ends at 100%
• Origin of the scale should be the center of the trigger (not the center of the tooltip) so it looks like it’s coming from it and not from itself.

In T360691#9882530, @ppelberg wrote:

Per what @egardner shared in Slack the latest OOUI release will NOT include a change to rem units.

I've updated the task description to reflect this.

We are pursuing a scaled-back solution now, and I've updated this task accordingly.

In T360691#9871593, @ppelberg wrote:

In T360691#9861561, @egardner wrote:

In T360691#9861330, @ppelberg wrote:

Per today's meeting with @Esanders, @Jdrewniak, @ovasileva, work on this task is blocked on DST merging the REM and dark mode changes into OOUI.

@CCiufo-WMF / @egardner: could y'all please comment here once the above is done so that the Editing Team knows when testing can begin?

Hi @ppelberg – our goal is to finish up the work in OOUI this week, cut an OOUI release at the beginning of next week (tentatively called 0.50.rc-1) and then ship that to beta right away.

All that you described above sounds great, @egardner.

Would it be alright for the Editing Team to expect a comment here y'all when everything is ready for testing by way of it landing on beta?

In T360691#9861330, @ppelberg wrote:

Per today's meeting with @Esanders, @Jdrewniak, @ovasileva, work on this task is blocked on DST merging the REM and dark mode changes into OOUI.

@CCiufo-WMF / @egardner: could y'all please comment here once the above is done so that the Editing Team knows when testing can begin?

We've done the first part of the acceptance criteria listed above.

In T365748#9848864, @lwatson wrote:

The design and feature updates from this task mention changing the logic behind the selection of menu items. As per ARIA APG, we'd need to (1) clear the previously selected menu item, (2) focus on the first menu item when the menu opens, and (3) update the keyboard navigation. Do we expect these changes to be part of the acceptance criteria for the current sprint before taking the MenuButton out of WIP?

cc: @egardner @bmartinezcalvo