summaryrefslogtreecommitdiff
path: root/addons/web/static/lib/jquery.mjs.nestedSortable/jquery.mjs.nestedSortable.js
diff options
context:
space:
mode:
authorqsm-odoo <qsm@odoo.com>2016-08-08 10:46:12 +0200
committerqsm-odoo <qsm@odoo.com>2016-08-08 11:03:29 +0200
commitfd7f0195332816cc057ac143397e7272cd8580b3 (patch)
treee3d1ac9bb7a5452144ab807167ea3efaac36e898 /addons/web/static/lib/jquery.mjs.nestedSortable/jquery.mjs.nestedSortable.js
parentf3e577da2f479d5d0b768bd6f217d5891c659915 (diff)
[FIX] web: properly position invisible elements in editable listview in modals
When positioning an element in an editable list view, that element is temporarily forced to display: block thanks to the class o_temp_visible The rule is written in LESS thanks to: .o_list_editable .o_temp_visible { display: block!important; } which is ok for normal invisible form fields because it is written as .o_form_view .o_form_invisible { display: none!important; } which has the same priority but is defined before the o_temp_visible rule, so the display is properly forced to block. However, for some reason, there also is the rule: .modal .modal-dialog .o_form_invisible { display: none!important; } which has a higher priority than the o_temp_visible rule. This is why appearing invisible fields in editable list view in modals are at a wrong position. The solution introduced by this commit is the safest: adding a new rule to force display block!important on the selector: .o_list_editable .o_temp_visible.o_form_invisible
Diffstat (limited to 'addons/web/static/lib/jquery.mjs.nestedSortable/jquery.mjs.nestedSortable.js')
0 files changed, 0 insertions, 0 deletions