@egardner @Volker_E I've got patches up for Sandbox demos and a fix. Pixel testing also needs to be done.

@Catrope @egardner the first acceptance criterion is complete. I also think it's worth considering whether menus within Tables should be able to extend beyond the boundaries of the Table. If that seems beyond the scope of this task, you could open a new one.

@Catrope do you remember why you implemented the initialPlacement fallback strategy way back in this patch? I'm trying to figure out if it's needed - it's messing up the MenuButton behavior, and doesn't seem necessary for other components IMO but I'm not sure.

I submitted a patch with a new demo that reproduces this behavior in the Sandbox so you don't have to spin up MPIC to see the bug. There are 2 issues here:

@CCiufo-WMF yes, and I plan to talk to the engineering team about this tomorrow during our synchronous meeting. We'll want to think through the potential for regressions and a testing plan, as you said.

This is a flexbox thing, and is not specific to InputBox - it could happen anywhere a button is used in a flex layout. It's also not related to the text truncation within the Button component.

In T368443#9936923, @lwatson wrote:

2. Per our TypeaheadSearch guidelines (specifications and best practices), we strongly discourage customizing the button label and encourage the label to be "Search" or its appropriate translation. Should we continue to allow customization if it goes against our guidelines?

@Catrope sorry, I missed up the two tasks!

Sorry @lwatson, I forgot to claim this and move it to "code review" when I opened the patch!@

Initially thought 2, but bumped to 3 in case we want to include:

• only adding necessary messages when code splitting is used (worth it? maybe not)
• testing

Tagging you all since this is a potential breaking change for Codex 2.0

Specific to the indication of scroll part:

Great, thanks @bmartinezcalvo and @DTorsani-WMF! I'll update my patch to:

• Keep the menu open on select
• Add the check icons
• Add deselection by re-clicking an option

In T363416#9893964, @mwilliams wrote:

Curious if this would/should/could support a lookup as well? That is a use case (https://phabricator.wikimedia.org/T366325) that may needed for metrics platform