diff options
| author | qsm-odoo <qsm@odoo.com> | 2017-04-19 13:06:05 +0200 |
|---|---|---|
| committer | qsm-odoo <qsm@odoo.com> | 2017-04-19 15:33:40 +0200 |
| commit | c33e535707299f67a1d35c39ca06d5341b468083 (patch) | |
| tree | be95185f29a7ac6ee269b97110b359e346ff7544 /addons/web/static/src/js/services | |
| parent | 9bf3e2a7fa1a97d91d37b0fb8f5e197de12feb89 (diff) | |
[FIX] web: modifiers on <footer/> tag in form
Since the new views, buttons were extracted of the <footer/> tags and
placed directly in the buttons area. While this would be a good idea,
this was ignoring the modifiers placed on the <footer/> tags. Multiple
solutions were possible:
1) Leave the <footer/> tag as it is (like before the new views)
This creates an useless <footer/> element in the DOM most of the
time.
2) Propagate the <footer/> modifiers to its children.
This requires some code to do the propagation and a modifier might
be evaluated multiple times for nothing (for each child).
3) Allow only one <footer/> tag in form views and divide buttons in
child <div/> elements.
Only creates the necessary DOM elements and modifiers are evaluated
only once.
While the third choice is obviously the better one, this commit is
implementing the first solution. Indeed, changing all the XML views
might not be a good idea in the current state.
Diffstat (limited to 'addons/web/static/src/js/services')
0 files changed, 0 insertions, 0 deletions
