diff options
| author | Aaron Bohy <aab@odoo.com> | 2020-07-02 11:52:07 +0000 |
|---|---|---|
| committer | Aaron Bohy <aab@odoo.com> | 2020-07-02 13:57:37 +0000 |
| commit | e17dc1a793817c535863d2e3e40754468d140fb8 (patch) | |
| tree | 7978e66ef4df645c1c8a3c416475e7ee365a34d9 /addons/web/static/src/js/views/abstract_controller.js | |
| parent | 25258e314e3a6fc97c072d5b7cb4236ac4fd5b01 (diff) | |
[IMP] web: form: labels of several occurrences of a field
Before this commit, when the same field occurred multiple times in
a form view, all occurrences were associated with the same id, and
all occurrences of the corresponding label (if any) had the same
'for' attribute. As a consequence, besides the fact that there were
warnings in the chrome console, clicking on any occurrence of the
duplicated label focuses the first occurrence of the field.
This commit generates a unique id for each pair label/field, when
possible. However, there is a case that can't be handled
automatically: when the label isn't automatically generated (field
located outside a group, or with nolabel attribute set to "1").
Typically, in this case, there is a <label> node with "for"
attribute referencing the associated field. In this situation, the
id must be defined in the arch, and used in the "for" attribute:
<form>
<label for="phone"/><field name="phone"/>
<label for="phone_2"/><field name="phone" id="phone_2"/>
</form>
Task 2261697
Diffstat (limited to 'addons/web/static/src/js/views/abstract_controller.js')
0 files changed, 0 insertions, 0 deletions
