summaryrefslogtreecommitdiff
path: root/addons/web/static/src/js/views/basic/basic_controller.js
diff options
context:
space:
mode:
authorGéry Debongnie <ged@odoo.com>2018-03-07 14:02:14 +0100
committerGéry Debongnie <ged@odoo.com>2018-03-12 13:53:39 +0100
commite7fab234201e357da52c3576ad2e8fc9ceee9359 (patch)
treec6b1a4daa31a157088b13c9f57a28c4ace6f8646 /addons/web/static/src/js/views/basic/basic_controller.js
parent96ebf00ca88d70f90294616bac6147822f5cac89 (diff)
[FIX] web: better experience for one2many edition (paged)
A big problem with the o2m edition happens when the user has a full page (so, in general, 40 records) and click on add. If the o2m is in editable="bottom" mode (which is actually a really common usecase), then the next record will be added at the end. However, since we have a limit of 40, it will immediately go to the next page. The effect is even weirder when there is a required field in the tree view. In that case, the new record appears correctly, the user can edit it, then, as soon as the required fields are set, it will immediately disappear from the current screen. In this commit, we have a really simple solution: we simply increase the limit in this case. An interesting thing is that it is actually temporary: when the user goes to the next page, the limit is back to its original value (due to the pager click: it resets the value to what the pager knows).
Diffstat (limited to 'addons/web/static/src/js/views/basic/basic_controller.js')
0 files changed, 0 insertions, 0 deletions