summaryrefslogtreecommitdiff
path: root/addons/web/static/lib/jquery.mjs.nestedSortable/jquery.mjs.nestedSortable.js
diff options
context:
space:
mode:
authorDamien Bouvy <dbo@odoo.com>2016-09-05 14:48:37 +0200
committerDamien Bouvy <dbo@odoo.com>2016-09-06 08:52:57 +0200
commit29d8576b0a9e41b922489e193ae4bb32e0b30fad (patch)
tree478aacad827510d844bf5c9e6bbadfc8185f0c87 /addons/web/static/lib/jquery.mjs.nestedSortable/jquery.mjs.nestedSortable.js
parentb9e31f132f92b27c07727706f083a6aeeb18b1df (diff)
[FIX] mail: remove duplicate code
There already is a redirect implementation in the chat_manager which closely matches the on_redirect implementation in chatter.js, however the former has the advantage of calling get_formview_id to ensure that the view is correct. This fixes a faulty behaviour when some models are referenced from chatter message using data attribute data-oe-model and data-oe-id. For example, linking invoices in the chatter would always open them with the 'vendor invoice' view; from this revision on the correct view will be used (assuming get_formview_id is implemented on the model). The default behaviour of the chat_manager when a user clicks on a partner record is to open a channel if the partner has a user then return a callback passed as a parameter (usually to open the channel as a popup or in the discuss app). To keep the old behaviour of the chatter followers list widget (i.e. open the partner form when clicking on a follower), a small change has to be made on the redirect implementation: when no callback is provided, do not create the channel (instead a returning an empty callback).
Diffstat (limited to 'addons/web/static/lib/jquery.mjs.nestedSortable/jquery.mjs.nestedSortable.js')
0 files changed, 0 insertions, 0 deletions