diff options
| author | Géry Debongnie <ged@odoo.com> | 2017-12-07 15:33:52 +0100 |
|---|---|---|
| committer | Géry Debongnie <ged@odoo.com> | 2017-12-07 16:20:46 +0100 |
| commit | 3b3f68030d29e74d3c2486921ed1b8868b1ba9c4 (patch) | |
| tree | aaa2c69f70f45c79210dee81ad77665d3ca1666c /addons/web/static/lib/jquery.mjs.nestedSortable/jquery.mjs.nestedSortable.js | |
| parent | e193926db0a3430e56db8e4eeeade70a7ea511f6 (diff) | |
[FIX] web: send proper context when fetching m2o namegets
When fetching batched namegets (typically after a default_get), we need
to evaluate the context that we send to the server. This may be
important for models with a custom name_get method. (note: overriding
namegets should be avoided if possible)
With the new views refactoring, this was not done properly and the
'view' context was sent instead. This is not really critical, the proof
is that it took a few months before getting some complaints, but this is
definitely a bug.
To reproduce, simply add a context attribute to a m2o field in a form
view, with a non empty value in a default get, and look at the context
sent to the server.
Diffstat (limited to 'addons/web/static/lib/jquery.mjs.nestedSortable/jquery.mjs.nestedSortable.js')
0 files changed, 0 insertions, 0 deletions
