Right hand 3-dot menu unclickable with scroll bar on Android Roon app [Ticket in]

[MattR]

What’s happening?

· Other

How can we help?

· None of the above

Other options

· Other

Describe the issue

Can't click right hand 3-dot menu when scroll bar present on Android Roon app

Describe your network setup

N/A UI/UX issue

[Mr.Flibble]

A screenshot may help here

[MattR]

I had attached a screencast showing the issue, but it seems it didn’t upload. Here’s a screenshot with a rough annotation. If the scrollbar overlaps any of the 3-dot menus they’re unclickable. Green check shows where it is clickable, red x shows unclickable.

[Mr.Flibble]

@MattR yes, I’ve noticed this also. On iPhone as well.

It’s hit n miss, but if you tap slightly over the track times does it bring up the menu?

@support this does seem to be more an issue on recent builds. As above I can replicate the issue and tapping slightly over the track time initially brings up the blue-ish play option menu, but then the 3 dot menu appears. The side scroll bar is huge by the way. Much bigger than I ever remember.

[MattR]

Yeah I can usually eventually get it to open, either by scrolling the screen so the scrollbar isn’t beside the track I want info on, or being very precise and clicking on the far right of track length which also seems to open it up.

Seems to be an issue with the tap target area being too small compared to the tap target width of the scroll bar. I understand why the scroll bar width is so wide, otherwise dragging the scrollbar would be hard to do unless grabbing super close to the edge of the screen.

A couple possible resolutions:

1. Move the button and track length further from the side of the screen.
2. Extend the 3-dot tap target much further to the left overlapping with the track length. So visually the button would be in the same place but you could get to it easier.
3. Handle tap vs drag differently. A single tap would go “through” the scroll bar to the button. Scrollbar would only handle hold+drag events

[vadim]

Hello @MattR,

We’ve discussed this with our senior QA and development teams. The team is investigating some possibilities here and, as soon as that investigation is complete, we’ll be sure to follow up ASAP.

You have our apologies for the trouble here, and we’ve greatly appreciated your patience as we continue investigating this tricky issue. We’ll be in touch as soon as we can.

[vadim]

Hey @MattR

Thanks for performing that test, we have added this info to the investigation ticket. The ticket has been submitted for developer review, meaning that this may take some time to be reviewed.

There aren’t any additional details needed at this time, so we will go ahead and close the thread for the time being, and if any other questions arise after the developers have reviewed the case, we will re-open the thread and reach out once more.

Thanks again for your report, and thank you in advance for your patience as the ticket progresses through the development queue for review.