Before this commit, the web client did not properly destroy field widgets when updating a one2many after an onchange. This is rarely an issue, because in general, there are no other field widgets besides the row currently in edition. However, if we specify explicitely a widget, or if we use a custom widget, it may be a problem.