Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
J
jami-client-gnome
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 153
    • Issues 153
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Requirements
    • Requirements
    • List
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • savoirfairelinux
  • jami-client-gnome
  • Issues
  • #407

Closed
Open
Opened Jan 20, 2016 by RingBot@RingBotOwner

GNOME: chat/call views don't seem to always get properly destroyed

Issue generated from Tuleap's migration script. Originally submitted by: Stepan Salenikovich (ssalenik)

There are 2 symptoms indicating this:

  1. sometimes new text messages received by a non-selected CM are marked as read
  2. the preview video is rendered very choppy

Normally, there should only be one view at a time... either a chat view or a call view. When switching between items in the recent model or switching the item state (call <-> chat) the old view should be destroyed. If it is not, it may continue to render video or mark messages as read.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: savoirfairelinux/ring-client-gnome#407