on change must be fired (again) after m2o returns with/after changes

[Ferdinand]

example
create SO
select product (without defined Sale VAT )
open product, add vat + save
IMHO now the VAT should show up in the sale form, but it does not

workaround , change product or delete and recreate line - not user for users

[Xavier (Open ERP) (xmo-deactivatedaccount)]

This is not a bug, the semantics of onchange are that the field's *value* changing triggers the call. Not the value of something somehow linked through the field.

[Ferdinand (office-chricar)]

this is a regression
version 6 and prior caused the on change trigger to be fired ALSO after returning from a (modified) m2o

[Xavier (Open ERP) (xmo-deactivatedaccount)]

It was never part of the field's semantics, and was rejected as a common-law feature.

[Ferdinand (office-chricar)]

As I said the behavior is different from 6.0 (GTK)
Example
Sales order
* select partner - this copies the payment terms into SO
* open partner - change payment term -
** in v6 and prior - the new payment term is copied
** in trunk the new payment term is not copied.

IMHO this change will cause major problems.

BTW the GTK trunk fires the on change also in v61
for this I reopen the bug again

[Antony Lesuisse (OpenERP) (al-openerp)]

Yes this is a common-law feature. But i think it should be implemented as there are no drawback to triggering an onchange a second time. And i agree that the use case presented by ferdinand should work.

[Raphaël Valyi - http://www.akretion.com (rvalyi)]

Hello I confirm that the last commit of https://code.launchpad.net/~openerp-dev/openerp-web/6.1-opw-577376-bth
fixed the bug for us. I'm not too sure if it introduces any regression yet, but at least it fixed the bug, so think about merging it please.

I will confirm here it introduces no regression. Regards.