Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in
QuasselDroid-ng
QuasselDroid-ng
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 66
    • Issues 66
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • External Wiki
    • External Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Janne Koschinski
  • QuasselDroid-ngQuasselDroid-ng
  • Issues
  • #119

Closed
Open
Opened May 31, 2018 by Shane Synan@digitalcircuit
  • Report abuse
  • New issue
Report abuse New issue

Dismissing notification marks entire buffer as read, not just highlights

Steps

  1. Connect to core
  2. Receive highlight in channel
  3. Receive non-highlights in that same channel
  4. Swipe away notification for highlight from that channel

Expected

The highlight status is removed from the channel, but the other messages are not marked as read.

Actual

The entire channel is marked as read, making it harder to see what messages may be missed.

Additional

This depends on protocol changes to the core, and may need the core-side notification system (not just core-side highlights) in order to mark notifications as dismissed without clearing a channel's activity.

Alternatively, Quasseldroid can mark everything up to the swiped-away notification as read, but this may risk confusion among users instead of the "swipe notification == marks all as read" behavior.

This could possibly involve messing with the last read markerline to re-set that to right after the highlight.. but that still risks confusion.

To upload designs, you'll need to enable LFS. More information
Assignee
Assign to
Future Release
Milestone
Future Release
Assign milestone
Time tracking
None
Due date
None
3
Labels
Blocked: Protocol Priority: Normal Type: Bug
Assign labels
  • View project labels
Reference: justJanne/QuasselDroid-ng#119