Some come was introduced to check status of test suite before creating a test result. This
introduced a regression in the case of cloud performance test. The code was covered by
unit test, but not in that particular case.

Separate css files for embedding during wkhtmltopdf pdf-conversion. only use ttf format to reduce payload.

/reviewed-on !690

Use the ERP5 router.
Allow pagination from one contact to another.
Allow to search a contact.

Stop using data url for images.

Update to Strophe 1.2.15

Experiment CSS customizations.
Show that it's possible to surcharge default CSS.

Create a dialog gadget used by most pages.

Use a grid of module's group to simplify navigation.

Only use hardcoded limit when rendering a listbox.

Always try to fetch the first 1000 documents in such case, and split the sql result in python.
This means that it is not possible to paginate to the 1001th document.

This MR will give similar behavior for Historical Comparison List in the new UI, which currently is broken.

/reviewed-on nexedi/erp5!683

Instead of sleeping, try using an API method until it stops raising
ConnectionError.

/reviewed-on nexedi/erp5!650

Removing one query improves the speed of the UI.

The goal is to reduce the number of HTTP query triggered by the UI.

Keep the original link to ensure compatibility with the UI.

Remove related scripts.

Module action is not a template anymore.

Speed up all calculations.

Do not access the document to modify. Using their UID is enough.
Rely on the listbox which send the list of UIDs when submitting the dialog.

Calculate the list of possible transition by inspecting the portal_workflow configuration.

Do not revalidate the form box twice.

[erp5_core] Use _your validator prefix

This will prevent double concurrent submit.
Mutex can not be used, as it will block the update rendering.

Disable the dialog until the event listener is actived.

Support dialog form box (with your_ fields)

This reverts commit 823842e1

As module may not have the same permissions as its sub-documents

We have a general rule not to really delete content, but for categories and web sections I feel it's different.

( there is [#704](https://nexedi.erp5.net/bug_module/704) but it seems it was a different issue at the time )


/reviewed-on nexedi/erp5!519