The method onchange() executes onchange methods in cascade.  Suppose onchange()
is called and a field F=1 in the form.  If an onchange method set F=2, that
value is put in the result variable.  If another onchange method set it back to
F=1, the binding F=2 must be removed from the result variable.

Fixes #2309

Move invisible field on bottom to avoid blank space in view if display journal, group or sequence field

Those values were dropped at rev 9b343581 but
need to be forced to empty so older databases
get fixed when upgrading

Those values were dropped at rev 3b636a5d but
need to be forced back to default so older
databases get properly updated when upgrading.

[FIX] hr_recruitment: fixed computation and storage of day_open and day_close + assignment of date_open and date_closed.

At 96f038a6 product-related fields were removed due
to an important product.template/product.product
refactoring. As the field values were simply
dropped, they may not be nullified when upgrading an
existing database. Forcing them to False will take
care of it.

This ensures the field values are cleared during
upgrades from previous versions

[FIX] point_of_sale: chrome was dropping the cookie when loading the company logo, resulting in an incorrect logo in multi-db setups.

Cascading onchanges can be caused by a related field computed in cache.  This
causes a bug in sale order lines, were setting the uom field forces reading
product fields, which are inherited from product templates.  The inherited
fields are computed as related fields, which marks the product record as dirty.
This subsequently triggers an onchange on the product field, which resets the
uom field!

[FIX] point_of_sale: prevent the company logo from being cached by the browser by accessing it via a random URL

Revert "[FIX] web: base.css: fixed width for input of file type under oe_avatar"
A better fix for opw-613318 is done in f8bd25c8

Before this, the div wasn't in the right place in the form view
for instance, in the product form view, the third checkbox triggered this binary upload file
opw-613318
task-8982

Fixes #2257

[IMP] Add possibity to add rereserve button and optimize action assign

[FIX] website_sale: Price of accessory product are all time null. Need to use new api to send the context.

[FIX] website_event_sale: need to use new api to send the context. Add some step for test to check if the cart have the distinct products

[FIX] website.editor: need to set the range on start because the browser can be lost the caret and can't insert the media in the page.

This fixes issue #2146.  The inverse of a one2many field can be an inherited
field (_inherits).  In that case, we cannot read its value with a simple
database query.  Instead, we let the related field read it, but for performance
considerations we disable the prefetching of other fields.

There was a domain in 7.0 but it must be forced
to empty during upgrade, as the MRP BoM model
has changed.

The mapping old api → new api mistakenly takes the last positional argument as
the context (fields_view_get() has an extra parameter after context.)

Fixes issue #2063

When no order is forced, it's more user-friendly if the products are ordered by alphabetical order.
This will mainly be applied:
* In the list view in the back-end
* In the eCommerce, for products with equal website_sequence

The context may be inconsistent (for instance, containing a group_by associated to another
model). The client will take care of keeping it consistent. Fixes issue #1768

name_get() must return a value for each ids and keep order of ids.

The methods product_id_change() and uos_id_change() have been converted to the
new api, and now use the decorator @multi.  When invoked with the old api, by
convention the methods will take the last argument as the context.  But this
will not work properly for those methods, as the context is passed in another
position.  In order to avoid an argument swap in the api wrapper, we moved the
context to its expected position.

Fixes #1943

The compatibility issue with auth_ldap has been
fixed and the default key derivation function
switched to PKDF2+SHA512. `auth_signup` provides
a password reset mechanism that can be used in
combination with `auth_crypt`.

Fixes #1272