Multi static select dropdown wont open again after selecting an option

[michaelbudgell]

Description

Hello,

I am having an issue with the multi-select. Whenever I select any option from the menu (on desktop) the menus dropdown will not appear for me again to select a second option. This has caused some confusion for users as they know they need to select multiple items but can't access the dropdown again after the first selection. My workaround thus far has been to type in the option you're looking for and the dropdown will appear again and populate with search results. I have noticed if you click into another box and back into the multi-select it may or may not work, but it's definitely not as intended.

What type of issue is this? (place an x in one of the [ ])

• [ x ] bug
• enhancement (feature request)
• question
• documentation related
• example code related
• testing related
• discussion

Requirements (place an x in each of the [ ])

• [ x ] I've read and understood the Contributing guidelines and have done my best effort to follow them.
• [ x ] I've read and agree to the Code of Conduct.
• [ x ] I've searched for any related issues and avoided creating a duplicate issue.

---

Bug Report

Filling out the following details about bugs will help us solve your issue sooner.

Reproducible in:

package version: Slack/bolt 3.11.1

node version: 18.2.0

OS version(s): MacOS 13.0.1

Steps to reproduce:

1. Make a multi-select with several options
2. Select any option
3. Menu/dropdown will not drop down after the first selection or if it does, it is finicky and won't stay open.

Expected result:

Drop down menu should continue to appear with every click of the box.

Actual result:

The drop down does not appear and the only way to select multiple items is to type them in.

Attachments:

Video: https://drive.google.com/file/d/13689zwlxYHxxPD_jhuWv07QuE1JF2FQI/view?usp=share_link

[srajiang]

@mjcbfl Thanks for reporting this and for providing the video link. This is definitely a Block Kit behavior and not related to the bolt framework per say, so I will report the behavior to the teams responsible. I'm not clear at this point on whether behavior like this is intentional, I will try to find out (though I do agree it seems wonky)

In the meantime we will keep this issue open in case others are experiencing a similar behavior and are looking for workarounds.

[srajiang]

Confirmed that it's an unexpected behavior and that we've got an issue filed for it internally.

[michaelbudgell]

Hi Sarah, Thank you for the quick response! I didn't realise different teams worked on them or I wouldn't have bugged ya'll. All the same, I appreciate you getting it looked into! Regards, Mike.

[MiesnerJacob]

I am now dealing with this exact same issue in my application. I have attached a video file showing the behavior. Was the internal ticket referenced in this thread ever resolved?

Screen.Recording.2024-03-01.at.10.46.33.AM.mov

[michaelbudgell]

I've also continued to have this issue!

…

On Fri, Mar 1, 2024 at 12:18 PM Jacob Maximillian Miesner < ***@***.***> wrote: I am now dealing with this exact same issue in my application. I have attached a video file showing the behavior. Was the internal ticket referenced in this thread ever resolved? https://github.com/slackapi/bolt-js/assets/47899591/38608bda-bd00-40cb-b2bd-f09d64fa89cc — Reply to this email directly, view it on GitHub <#1706 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AUVXOZKYWWYYYA4MRISE7BLYWCPLXAVCNFSM6AAAAAATRMJBXSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZTGQZDGMRZGQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>