This improves the performance of prefetching fields for large recordsets.

Incomplete senstense "improving applications, such as the"
Will be fixed in master, creating en_US translation for stable

not enterprise + community

Fix typo in description string (was already done in enterprise)

Introduced by 72e94bee

opw:651811

Issue: already selected ids are not filtered in the many2one and appear in the dropdown (but can't be select because the item are already selected)

The filter "Followed by Me" depends on a calculated field is not stored.
Therefore, we need to redefine the search method.

Fixes #8920

The introduction of the CSRF tokens in
8932c52e broke invoicing from the Point
of Sale. chrome.do_action('point_of_sale.pos_invoice_report') would
fail because no CSRF token is set in the POS. This fixes it using a
similar approach as in the website module.

Revert "[FIX] sale: when creating a refun from an invoice, the invoice lines must be linked to the original so lines to compute the invoiced quantity correctly"

This reverts commit a315487c. Apparently it was 💩.

In case the product is a service, no move_ids are linked to it, and
the quantity delivered is never calculated.

[FIX] stock_account: added a property for valuation journal, for yaml tests that needs to create accounting entries

[FIX] purchase: fixed wrong test. The account on vendor bill should be the payable account of the partner, not the expense account of the product

[FIX] stock_account: do not create the property for stock input account for the product category 'All' because a categry does not inherit from its parent properties (anymore?). Fixes purchase test failing for companies running anglo saxon accounting

[IMP] base: only recompute `share` field on users when users are added/removed from group "Employee"

Note: The change in `base_security.xml` is needed as xmlid must exists
when adding/removing users from group to determine the value of `share`
field.

Also add a test to reassure @odony the function fields are correctly
recomputed for removed m2m entries (see http://git.io/vCqAG for context)

The `analytic_account_id` was set after the field `active`.
This `active` field has been moved, to the top of the form,
in a button, at revision ed95043d.
Placing the analytic account after this field is
therefore no longer the brightest idea.

In addition, there is no longer any `parent_id` field
on the `account.analytic.account` model, making the according
domain invalid.

Fixes #8668

Creating a en_US translation to avoid breaking existing translations

Fixes remaining occurences of 8.0 in the windows installer. Mainly, odoo is now
correctly installed in odoo.9.0-timestamp/ instead of odoo.8.0-timestamp/

Reduce the number of calls to `search` by grouping fields by model and by path.

The lost filter wasn't working:
 - The domain syntax was not correct
 - It tried to filter `active='f'` leads,
   while, in the SQL view, they were already filtered out
   with `active='t'`

We can safely remove the active=`t` from the SQL view, by default
`active='f'` records are filtered out except if explicitely set
otherwise.

opw-651746

Hopefully one last time and not one more time...

[FIX] sale: when creating a refun from an invoice, the invoice lines must be linked to the original so lines to compute the invoiced quantity correctly

Since invoice quantities are computed from the invoice lines linked to the so line via a many2many field, we need to overload the refund function that adds the fields on the invoice lines; explicitly copying the sale order lines references.

[FIX] stock_account: anglo saxon mode account switch for supplier invoice should not be triggered for service products

Fiscal position might be a good name in the backend, but it's confusing
for POS users.

With permission from @mart-e.

This reverts commit 9d56450d.

Enterprise makes use of these views. Anyway, views should not be removed
in stable.

Some usability improvements. A field "Purchase Order" is added on the
invoice line, so it is much easier to make the link between the invoice
line and the PO.

On the other hand, the "Purchase Order" field which was used for
encoding help is kept empty since it is not meaningful.

If the default_sale_tax_id or default_purchase_tax_id is removed from
the settings, the ir.values must be updated accordingly (i.e. set to
False). Otherwise, the value will come back when the page is reloaded.

Remove useless groups group_analytic_account_for_purchases and
group_analytic_account_for_sales.

This reverts commit 85f6b7c0.

This commits prevents creating a new database

When using the tab key on non text node range, it could fail in some
given case.

Also when removing the last element of the table row, a correction was done in
d33086c0 but if there was no element before the table (eg. the editor
is empty) an error could occur.

Tests for null range were not done in #8845, so in given case (where the
focus is not in the editor) we could get an issue.

The code for remembering the selection when clicking the editor
was made useful in d33086c0, but there was an edge case when
the editor itself was in a modal: then the selection would be lost.

This commit change the code as following:

1) restore the selected range if:

- the current selected range is not in the editable of the active editor
- there is a corresponding saved selected range or we are in an embeded
  editor (and not in air mode as when editing the website)

2) save the selected range if:

- we don't restore the selection,
- the current selected range is in the active editor editable area

The range can be null if the focus is not in the editor at serveral
places.

closes #8845