Skip to content

fix: use desktop message menu trigger on mixed input devices #680 #682

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
szuperaz merged 1 commit into from
Jan 21, 2025
+4 −1
Merged

fix: use desktop message menu trigger on mixed input devices #680 #682

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion projects/stream-chat-angular/src/lib/message/message.component.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,6 +38,7 @@ import {
NgxFloatUiLooseDirective,
} from 'ngx-float-ui';
import { TranslateService } from '@ngx-translate/core';
import { isSafari } from '../is-safari';

/**
* The `Message` component displays a message with additional information such as sender and date, and enables [interaction with the message (i.e. edit or react)](/chat/docs/sdk/angular/concepts/message-interactions/).
Expand Down Expand Up @@ -98,7 +99,9 @@ export class MessageComponent
};
areMessageOptionsOpen = false;
canDisplayReadStatus = false;
hasTouchSupport = 'ontouchstart' in window || navigator.maxTouchPoints > 0;
hasTouchSupport = isSafari()
? 'ontouchstart' in window || navigator.maxTouchPoints > 0
: window.matchMedia('(any-hover: none)').matches;
private quotedMessageAttachments: Attachment[] | undefined;
private subscriptions: Subscription[] = [];
private isViewInited = false;
Expand Down