Odoo/addons/web/static/tests/control_panel, branch 14.0

[FIX] web: allow custom filters by ID interval

2021-05-28T13:37:52+00:00

Infinite number of records cannot be exported, so after some limit we will get a
timeout error. If you need to export more records than that limit, you should be
able to filter records into batches. The easiest way to do it is making a
filter by ID:

```
[Y| ID Greater than 100000] [Y| ID less than or equal to 200000]
```

---

opw-2517946

closes odoo/odoo#71345

X-original-commit: 2e0127af0d283d1d9bdb033de356e2ddf0973cce
Signed-off-by: Aaron Bohy (aab) 
Signed-off-by: Ivan Yelizariev // IEL

[FIX] web: allow filtering with decimals on price filter + unit test

2021-03-15T14:27:56+00:00

Issue

	- Install "Sales"
	- Switch to "German" language
	- Go to Sales -> Products -> Products
	- Try to filter on "Public Price" is equal to "2,3"

	Not possible to add decimal point at the end (only in middle of number).

Cause

	In case the 'decimal point' in DB params is not a dot '.',
	the filter input will be considered as 'text' instead of
	'number'.

	In case of the 'number' type; HTML do already a pre and post
	processing, including managing decimal point (who, for example,
	is not included in ev.target.value if last char is a '.').
	Unfortunalty, the library is not well working with other
	language and not supported on every browser, therefore,
	must use own logic.

	In case of a 'text' type, the value will be send to 'parseFloat'
	,then `parseNumber` will replace decimal_point by dot (also one the
	issues since needed to display decimal_point according user language),
	and `Number` will remove the decimal_point in case of '123,' -> '123',
	and therefore we will not be able to write decimals ( apart of adding
	the decimal point after writing the whole number...)

Solution

	If user input is well parsed, store parsed value in condition.value and
	set condition.displayedValue to the input value (an so without updating
	input value). Else, replace input value with previous value (who should
	be the condition.DisplayedValue).

opw-2463441

closes odoo/odoo#67767

Signed-off-by: bon-odoo

[FIX] web: boolean field autocompletion with 'No'

2021-02-12T09:22:50+00:00

Before this commit, select the "No" option of a boolean field in the
search bar autocompletion menu would crash.

closes odoo/odoo#65896

Signed-off-by: Aaron Bohy (aab)

[FIX] web: keep null/false/true strings in domains

2021-02-11T09:20:26+00:00

Before this commit, occurences of 'null', 'true' and 'false'
strings as autocomplete values in the search view were replaced
respectively by None, True and False.

Fixes #65743

closes odoo/odoo#65900

X-original-commit: 74311c753e7286c27b83dca2b598e040ed9e586f
Signed-off-by: Géry Debongnie (ged) 
Signed-off-by: Aaron Bohy (aab)

[FIX] web: use latin number date domain in comparison menu

2020-11-05T15:42:28+00:00

When using eg. arabic locale, the figures inside dates were replaced by
arabic figures which are not supported server side (they are almost
always sent in latin figures).

With this changeset, the we are using english locale to get date in
domains.

Without the change, added test fails with:

  Numbers in domain should not use addoneForTest locale
  Expected:...[date_field, >=, 2020-06-01], [date_field, <=, 2020-06-30]
  Result:...[date_field, >=, 3131-17-12], [date_field, <=, 3131-17-41]

opw-2370392
closes #61354

Signed-off-by: Nicolas Lempereur (nle)

[FIX] web: load_filters in search dialogs

2020-10-06T07:17:43+00:00

Since fbf347498f1cc7b74ef373179b7bcae201715c24, when opening a view in a
dialog, the favorite filters were not loaded.
For example on the runbot:
1. In CRM, open any lead, edit it, and open the Customer dropdown
2. Create a custom filter, save it as favorite, and close the dialog
3. Open the dialog again: you don't see your new filter

With this commit, you will see your filter at step nr. 3

closes odoo/odoo#59180

X-original-commit: 418013e8dbb2aa2d4ffd4f650f080ca5a94183f9
Signed-off-by: Aaron Bohy (aab) 
Signed-off-by: Paul Morelle

[FIX] web: remove uppercase under Favorites

2020-08-26T05:17:00+00:00

this commit removes unnecessary uppercase used under the favorites menu

task - 2325684

[FIX] web: default operators for search fields

2020-07-31T08:04:57+00:00

During the refactoring of the control panel (https://github.com/odoo/odoo/pull/41268)
a regression concerning the operator used for the fields set as
search_default was introduced: the default operator was fixed to '='
while it would have been necessary to take into consideration the
optional 'operator' attribute or the field types. Moreover, the default
operator associated to many2one fields when using autocompletion was
also mistakenly set to 'ilike' instead of '='. The present commit
restores the previous behavior.

closes odoo/odoo#55099

X-original-commit: 1f8e93fc590a6c7ef6b93953058f2dcd643ac620
Signed-off-by: Aaron Bohy (aab) 
Co-authored-by: Julien Mougenot 
Co-authored-by: Mathieu Duckerts-Antoine

[IMP] web: Drop widget support in search view

2020-07-27T08:03:18+00:00

Until now the "widget" attribute used in the search view was meant to
force the type of a field regardless of its definition. This system was
implemented quite a long time ago and is now useful in only one case:
searching for "reference" fields (we want them considered as char fields
else it is impossible to search on them).

This is why this commit completely removes the "widget" attribute
support in search views while consistently casting the "reference"
fields as "char" fields in the search bar.

Task 2061795

[IMP] *: adapt tests to Owl search panel

2020-07-23T08:21:10+00:00

Adaptation of the tests to the changes regarding the refactored search
panel and model.

Part of task 2228968

Co-authored-by: Julien Mougenot 
Co-authored-by: Mathieu Duckerts-Antoine