-
-
Notifications
You must be signed in to change notification settings - Fork 655
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.
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
Click on notification should expand it #5242
Comments
Hello. can I work on it? can you please guide me a bit? |
@Tusharkhati please refer to the Zulip contributor guide and linked resources for some advice no how to ask for help. As mentioned in the guide:
Thanks! |
@gnprice would I get help on how to go about solving this issue? I had checked NotificationListener.js, notifOpen.js, notifToken.js files getting no idea where to look for. |
This part of the UI is one of the small number of places controlled by our Android-native code. The relevant source file is: For background on the Android-native code, see: |
|
Ah, yeah, perhaps we'll get back to doing that (or something like it) someday. 🙂 I've just assigned the issue to you; please let me know if you have any questions! |
@chrisbobbe Is there a good way to trigger several notifications (apart from just waiting for them to roll in organically)? |
Hmm, good question. We've thought about adding a feature for requesting a "test notification" from the server when you press a button in the mobile app, so users can confirm on-demand that notifications are working. So far, we haven't picked up that work, though. My go-to solution so far has been to send PMs between my main account on CZO (chat.zulip.org) and a test account I created there. The "test here" stream or a new private stream would also work as an alternative to PMs, as long as notifications are enabled for the stream. |
Removes the summary notification from the group in NotificationManager.kt. This allows the user to tap on the body of the notification to open the app, which was not possible with the summary notification (only the chevron would expand the notification, which would then allow the user to interact with the individual notifications below it. Please note that removing the summary notification breaks proper grouping: multiple private messages from the same user will correctly be grouped together, but stream notifications appear in a separate notification. This was tested manually. Fixes part of zulip#5242.
Removes the summary notification from the notification group in NotificationManager.kt, and removes logic around removing the summary notification when Zulip messages are read. This change allows the user to tap on the body of the notification to open the app, which was not possible with the summary notification (only the chevron would expand the notification, which would then allow the user to interact with the individual notifications below it. Please note that removing the summary notification breaks proper grouping: multiple private messages from the same user will correctly be grouped together, but notifications for different stream conversations appear in separate notifications. This was tested manually. Fixes part of zulip#5242.
Removes the summary notification from the notification group in NotificationManager.kt, and removes logic around removing the summary notification when Zulip messages are read. This change allows the user to tap on the body of the notification to open the app, which was not possible with the summary notification (only the chevron would expand the notification, which would then allow the user to interact with the individual notifications below it. Please note that removing the summary notification breaks proper grouping: multiple private messages from the same user will correctly be grouped together, but notifications for different stream conversations appear separately. This was tested manually. Fixes part of zulip#5242.
Updating this with what we've learned from @rachelhyman's investigation (in chat thread and at #5459):
That latter behavior is what one sees with Gmail, or with the Messages app that on a Pixel device handles SMS by default. |
Adds an intent to the summary notification. When the summary notification is clicked in the collapsed state, the app will open and reset itself to the unreads screen. It will also switch to the appropriate account if needed. Because the intent flags (Intent.FLAG_ACTIVITY_NEW_TASK and Intent.FLAG_ACTIVITY_CLEAR_TOP) apply to both the normal notification and the summary one (and are prefaced with explanatory comments), I moved them to a variable before where both notifications are created. This was manually tested for the following cases, with both the app already being on the correct account and being on a different account: - App open in background on non-unreads screen - App open in background on unreads screen - App not open in background I also made sure that tapping on a notification in the expanded state still routes the user to the correct screen. Fixes zulip#5242.
On Android, clicking on a top-level notification currently does not do anything. The user needs to click on the caret menu to expand and show the individual topics, which can then be clicked to open in the app.
To make it easier for the user to open up the notification, clicking on a top-level notification should make it expand to show individual topics.
CZO discussion
The text was updated successfully, but these errors were encountered: