[Bug]: macOS long press on a message in a 1:1 chat does not open menu options

[foss-]

What Monal Release channel are you using?

Alpha

iOS system version (if applicable)

No response

macOS system version (if applicable)

15.7.2

Monal version

Alpha c808f04 (Dec 10 2025 09:12:41 UTC)

Used XMPP server (domain)

disroot.org

Which XMPP-Server software are you using?

None

XMPP Server Software Version

No response

How many accounts are you using in Monal?

1

What happened?

Long press on a message in a 1:1 chat does not open menu options on macOS. The window is blurred but no options are showing.

Anything else?

No response

FAQ

• I have checked the FAQ for my issue

Considerations for XMPP users

• I have checked if my issue can be solved with Considerations for XMPP users and Considerations for XMPP server admins

XEP-Check

• I have checked that at least XEP-198, XEP-0280, XEP-0352, XEP-0357, XEP-0313 and XEP-0163 are activated on my server and shown as 'green' under Settings --> Account--> (i) in advanced settings

Notifications-Menu

• I have checked that all checkmarks are present under Settings --> Notifications

[lissine0]

Does this only happen in 1:1 chats? Did you long press an incoming message or an outgoing one?

Can you make the Monal window smaller by decreasing its width? There's a bug where the message menu elements get rendered out of the bounds of the screen. I suspect that's what's happening here.

[foss-]

That indeed seems to be the case. When long pressing a received message that message is in focus showing copy + delete locally options. However no reaction option is shown. Overall this UI can't be right. Esc key allows to exit that view.

When opening a sent message the message seems to be fully off screen and no interaction options are seen whatsoever and also no reaction options.

[lissine0]

Yeah, this bug needs to be fixed in the chat UI library we're using (which wasn't built with macOS in mind)

By the way, there's a toggle in settings -> debug -> crash testing, which lets you enable / disable the new chat view, in case you want to use the alpha as your daily driver and need some functionality that wasn't implemented yet.

[foss-]

WIth the latest alpha build from today post reactions are now showing for sent and received messages, which is great. The UI is still not ideal, but the problem this issue here is about is resolved function wise.

You decide whether to close this issue or leave it open until additional UI finetuning happened.

[lissine0]

WIth the latest alpha build from today post reactions are now showing for sent and received messages

As far as I can tell, none of the commits since c808f04 changed anything that would cause the reaction menu to not appear.

If it did not appear for you earlier, it's possible that it was in a MUC that doesn't support occupantIDs (or occupantID support wasn't detected yet).
Monal requires occupantID support in rooms in order to enable reactions (and probably retractions and corrections as well).

As for the UI issue, I'm aware of it.
It needs to be fixed in the ChatUI library we're using (https://github.com/exyte/Chat/)
As I mentioned earlier, the library wasn't built with macOS in mind. That's why there are macOS-specific issues / missing features, like press-enter-to-send and this UI bug.

[foss-]

Just for the record: both scrennshots with and without reaction UI elements are from the same chat 😬

[lissine0]

Is it a group chat?
Are you still able to get a message menu without reaction UI?

[foss-]

Should have added that info right away. It's a 1:1 with the main dev 😀
Oddly I am still able now to open a view with no UI elements at all (or rather out of visible area). I briefly thought this might be related to internal screen vs external monitor but it is not. Currently I am seeing the UI elements on either screen.

[lissine0]

Since it's a 1:1 chat, the reaction UI was probably rendered, maybe outside the bounds of the screen.

Oddly I am still able now to open a view with no UI elements at all (or rather out of visible area). I briefly thought this might be related to internal screen vs external monitor but it is not.

The factors in this bug are your screen resolution and the width of the window. Here's a quick video to demonstrate that

Screen.Recording.2025-12-10.at.11.30.26.PM.mov

As you can see, when the window is too narrow, the reaction UI gets squished into a tiny rectangle. (You can see a similar rectangle in your second screenshot, at the left)

About not seeing any UI elements at all, that might be caused by the use of two monitors. You can confirm if that's the case by resizing the window and seeing if that helps.

[foss-]

Filed an issue with exytechat: exyte/Chat#241