summaryrefslogtreecommitdiff
path: root/addons/web/static/lib/jquery.mjs.nestedSortable/jquery.mjs.nestedSortable.js
diff options
context:
space:
mode:
authorAlexandre Kühn <aku@odoo.com>2019-01-14 17:19:14 +0000
committerAlexandre Kühn <aku@odoo.com>2019-01-15 12:17:24 +0000
commitabeb75ae6006b50dace9397db35c08c90f6cc568 (patch)
treecb7ff9f4f13ddb222f1d6e36e5d67410a99525c6 /addons/web/static/lib/jquery.mjs.nestedSortable/jquery.mjs.nestedSortable.js
parentdc12f7e06c4c7d10f17aa56e4ba482a9b126a0ce (diff)
[FIX] mail, im_livechat: no loose of livechats on page refresh
Before this commit, when livechat operators had chats in the Discuss app and reload their page, they could loose some pinned livechats. This problem only occurred on livechat conversations when both users are authenticated. Any two-user channels should always be pinned by default, which is the case for internal chats. This logic was applied on channels with type `chat`, but this is ignored with livechats because they are channels of type `livechat`. This commit fixes the issue by defining internal chats and livechats as `chat`. Any chat conversations are automatically pinned when a message is posted, including livechats. Note that before this commit, the livechats were visually pinned in the Discuss app, although the server did not consider them as pinned. The client-side code always assume conversations are pinned, which is why a page refresh looks like a loose of previously pinned conversations. opw-1919327 closes odoo/odoo#30200
Diffstat (limited to 'addons/web/static/lib/jquery.mjs.nestedSortable/jquery.mjs.nestedSortable.js')
0 files changed, 0 insertions, 0 deletions