diff options
| author | qsm-odoo <qsm@odoo.com> | 2017-03-24 14:39:09 +0100 |
|---|---|---|
| committer | qsm-odoo <qsm@odoo.com> | 2017-03-24 14:39:09 +0100 |
| commit | 1a40e7b6c7956987f469fb7b2159f297c69ef537 (patch) | |
| tree | 9c0eb84adfb7bab8bd18625500a2e00f6b8684c4 /addons/web/static/src/js/views/basic/basic_controller.js | |
| parent | b3934619d4688ea9019495ae6525f0e57416f5bb (diff) | |
[FIX] report: allow to use `Dialog` API in report editor
When editing a report, the editor is launched in an iframe with an
environment which is different from backend and frontend. The problem
here is that the editor uses the `Dialog` API while the report editor
was not loading the associated xml file this API needs to work. Indeed,
when clicking on the "Discard" button for example, nothing seemed to
happen as a dialog was supposed to be opened.
This worked before as the editor was not using the `Dialog` API until
commit 62fb1bb92493b00bd45ed3f4eced5ca8b23f81d6.
Unfortunatly, this commit adapted "iframe.js" to load the associated
xml file but forgot to adapt the report editor. In a future
amelioration, this "iframe.js" file could be added to the report editor
so that all "iframe editor" environement work properly with the same
adaptation code.
opw-724784
Diffstat (limited to 'addons/web/static/src/js/views/basic/basic_controller.js')
0 files changed, 0 insertions, 0 deletions
