summaryrefslogtreecommitdiff
path: root/addons/web/static/tests/fields/relational_fields
diff options
context:
space:
mode:
authorAaron Bohy <aab@odoo.com>2019-04-04 08:24:52 +0000
committerAaron Bohy <aab@odoo.com>2019-04-12 06:14:08 +0000
commitd971e4f4c7dfe0bba60828948174a399e4ebc4d3 (patch)
treea2259f3bf6bf5ecf0721eaf32c75d46cea02fbb7 /addons/web/static/tests/fields/relational_fields
parentf7432d0d0421bee30663c30a0ddbcc6a9cf62d9b (diff)
[FIX] web: x2many list: edit and long click 'Add a line'
Assume an x2many editable list where the user edits a record (input field), and then clicks on 'Add a line' (and keeps it pressed for a while, before releasing the click). When the 'mousedown' event occurs, the 'change' event is triggered on the edited field, and (once potential onchanges have been applied), the list is updated, i.e. all rows except for the one being edited a re-rendered. However, the 'Add a line' handler listens to the 'click' event, which never occurs if we release the click after the rows have been re-rendered. This is an issue for every rows, not only 'Add a line', but for data rows, the issue is already present in former versions, and is not that easy to fix). The 'Add a line' case is a consequence of the recent work on list views (see 234d92c4f0c0), so we can fix it independently. Task 1915702
Diffstat (limited to 'addons/web/static/tests/fields/relational_fields')
-rw-r--r--addons/web/static/tests/fields/relational_fields/field_one2many_tests.js59
1 files changed, 59 insertions, 0 deletions
diff --git a/addons/web/static/tests/fields/relational_fields/field_one2many_tests.js b/addons/web/static/tests/fields/relational_fields/field_one2many_tests.js
index 85975d99231..0a96e07310e 100644
--- a/addons/web/static/tests/fields/relational_fields/field_one2many_tests.js
+++ b/addons/web/static/tests/fields/relational_fields/field_one2many_tests.js
@@ -8290,6 +8290,65 @@ QUnit.module('fields', {}, function () {
form.destroy();
});
+
+ QUnit.test('one2many editable list: edit and click on add a line', async function (assert) {
+ assert.expect(9);
+
+ this.data.turtle.onchanges = {
+ turtle_int: function () {},
+ };
+
+ var form = await createView({
+ View: FormView,
+ model: 'partner',
+ data: this.data,
+ arch: '<form>' +
+ '<field name="turtles">' +
+ '<tree editable="bottom"><field name="turtle_int"/></tree>' +
+ '</field>' +
+ '</form>',
+ res_id: 1,
+ mockRPC: function (route, args) {
+ if (args.method === 'onchange') {
+ assert.step('onchange');
+ }
+ return this._super.apply(this, arguments);
+ },
+ // in this test, we want to to accurately mock what really happens, that is, input
+ // fields only trigger their changes on 'change' event, not on 'input'
+ fieldDebounce: 100000,
+ viewOptions: {
+ mode: 'edit',
+ },
+ });
+
+ assert.containsOnce(form, '.o_data_row');
+
+ // edit first row
+ await testUtils.dom.click(form.$('.o_data_row:first .o_data_cell:first'));
+ assert.hasClass(form.$('.o_data_row:first'), 'o_selected_row');
+ await testUtils.fields.editInput(form.$('.o_selected_row input[name=turtle_int]'), '44');
+
+ assert.verifySteps([]);
+ // simulate a long click on 'Add a line' (mousedown [delay] mouseup and click events)
+ var $addLine = form.$('.o_field_x2many_list_row_add a');
+ testUtils.dom.triggerEvents($addLine, 'mousedown');
+ // mousedown is supposed to trigger the change event on the edited input, but it doesn't
+ // in the test environment, for an unknown reason, so we trigger it manually to reproduce
+ // what really happens
+ testUtils.dom.triggerEvents(form.$('.o_selected_row input[name=turtle_int]'), 'change');
+ await testUtils.nextTick();
+
+ // release the click
+ await testUtils.dom.triggerEvents($addLine, ['mouseup', 'click']);
+ assert.verifySteps(['onchange', 'onchange']);
+
+ assert.containsN(form, '.o_data_row', 2);
+ assert.strictEqual(form.$('.o_data_row:first').text(), '44');
+ assert.hasClass(form.$('.o_data_row:nth(1)'), 'o_selected_row');
+
+ form.destroy();
+ });
});
});
});