Raphael Collet 2067a206ec [FIX] models: process onchange methods on new records in the order of the view ... The onchange() on new records processes fields in non-predictable order. This is problematic when onchange methods are designed to be applied after each other. The expected order is presumed to be the one of the fields in the view. In order to implement this behavior, the JS client invokes method onchange() with the list of fields (in view order) instead of False. The server then uses that order for evaluating the onchange methods. This fixes #4897.		2015-02-10 13:12:40 +01:00
..
css	[FIX] web: firefox print all pages of list view	2014-12-24 13:52:45 +01:00
font	[FIX] File permission: remove unnecessary executable perm on files	2015-01-23 11:11:27 +01:00
img	[FIX] Use local copies of png instead of fetching them from websites	2015-01-23 11:23:04 +01:00
js	[FIX] models: process onchange methods on new records in the order of the view	2015-02-10 13:12:40 +01:00
xml	[FIX] dbmanager: backup support both zip and pg_dump custom format	2015-01-19 02:05:12 +01:00