gnome-shell/js/ui/components
Florian Müllner a0868bac6b telepathyClient: Keep source alive while channel is open
Sources are destroyed with their last notification. This is usually the
correct behavior, however in case of chat sources, the corresponding
telepathy channel might still be open, and any further messages that
should trigger a notification are lost because chat sources are only
created when telepathy's channel dispatcher notifies us about a channel
(via ObserveChannels).
Loosing messages like this is unexpected, so keep chat sources around
even without notifications while the channel is open.

https://bugzilla.gnome.org/show_bug.cgi?id=747636
2015-04-11 22:53:42 +02:00
..
__init__.js Don't start new components when activating the screen-shield in gdm 2012-09-05 16:14:02 +02:00
automountManager.js js: Adapt to GSettings API change 2014-06-24 15:17:09 -04:00
autorunManager.js autorunManager: Provide a createBanner() implementation 2015-02-20 17:41:57 +01:00
keyring.js theme: clean up dialogs 2015-02-20 15:14:46 +01:00
networkAgent.js NetworkAgent: use existing strings to avoid breaking the string freeze 2015-03-12 22:23:57 +01:00
polkitAgent.js theme: clean up dialogs 2015-02-20 15:14:46 +01:00
telepathyClient.js telepathyClient: Keep source alive while channel is open 2015-04-11 22:53:42 +02:00