Skip to content
Snippets Groups Projects
  1. Nov 09, 2015
    • Ingo Bauersachs's avatar
      Merge pull request #161 from 459below/fix-callbutton · 57677312
      Ingo Bauersachs authored
      Fixes the contacts 'call button' disappearing on multiresource contacts
    • Timur Masar's avatar
      Option for new behaviour of detecting a contact's capabilities · 45d8ee64
      Timur Masar authored
      This reintroduces some old code in order to give the user the option to
      switch between those two behaviours.
      
      It also prevents the removal of all caps nodes (and thusly breaking the
      new detection) when a rogue offline presence event comes in. This is
      such an event in which a contact is falsely assumed as offline, if the
      preferred resource of two or more same prioritised resources goes
      offline. We are checking this by looking whether it is a
      "resourceChanged"-event. This should probably be changed again, after
      those offline presence updates have been fixed.
      45d8ee64
  2. Nov 08, 2015
    • Timur Masar's avatar
      Fixes the contacts 'call button' disappearing on multiresource contacts · 6fcbb766
      Timur Masar authored
      This changes the behaviour from "last connected resource" or "highest
      priority resource" to "most capable resource" regarding the display of
      buttons next to this contact. We now check every resource the contact
      has connected and we will consider the one with the most capabilities.
      This elimates the very frustrating scenario in which the call
      capabilites are disabled on a contact who connected additionally a
      non-jingle client.
      
      Note that there exists separate issue in which the contact logs off from
      only one resource, but gets displayed as completely offline. In that
      case the buttons are still displayed wrong, if the contact connects a
      non-jingle client on afterwards.
      6fcbb766
  3. Nov 05, 2015
  4. Nov 04, 2015
  5. Oct 27, 2015
    • Ingo Bauersachs's avatar
      Remove bundle start level conflict · f5dc6ede
      Ingo Bauersachs authored
      Fixes #162
      Fixes #163
      Fixes #172
      
      The build process injects an additional bundle at start level 14. This
      conflicted with the start level for commons-codec, preventing Jitsi to
      start. Felix' bundle cache might have prevented the bug from appearing
      for people who had a previous version running successfully.
  6. Oct 20, 2015
  7. Oct 16, 2015
  8. Oct 13, 2015
  9. Oct 10, 2015
  10. Oct 07, 2015
  11. Oct 05, 2015
  12. Oct 04, 2015
  13. Sep 28, 2015
  14. Sep 23, 2015
  15. Sep 07, 2015
  16. Sep 06, 2015
Loading