romain_dev: forum

romain_dev: forum use html viewer

romain_dev: forum improve post rendering

romain_dev: thread reader use page language inqtead of local

romain_dev: forum set expected link on the listbox cells

romain_dev: thread fixup

romain_dev: thread use line separator instead of background color

romain_dev: thread paginate

romain_dev: forum link to last page

romain_dev: thread simplify conf from erp5form

romain_dev: forum attachment

romain_dev: thread force white background

This reverts commit e50d05af.

Do not access form submission REQUEST from the listbox list method,
as it is rendered asynchronously in ERP5JS

Allow edition in the new UI

This make everything slow as hell and prevent to quickly save.

Example: <h2 class="foo">bar</h2> => <h3 class="foo">bar</h3>

erp5_web_renderjs_ui: keep previous focus color

If user group are recalculated before changing the workflow state, it will only return the same security group
See nexedi/erp5@c00c3636

Otherwise, a weird behaviour is observed with compound attributes (eg.
`xmlns:inkscape`), where the second part of the attribute is replaced by
`undefined`, giving a wrong SVG file when there are multiple attributes
(duplicate attribute).

Otherwise, method draw enter an infinite loop if users selected some elements

https://github.com/methodofaction/Method-Draw/tree/463e526dbc6ec48561822fde5dec02e085e86497

See merge request !2034

Infinite listbox are listboxes for which the "lines" property is set to 0, meaning the listbox shouldn't try
to paginate results.

This is intentional, and means that no limit should be applied (iow: an infinite
listbox). In this case, the limit parameter in the call to jIO should be set to 0,
not undefined, otherwise the parameter will be dropped in the AJAX request,
and later on be defaulted to 10 by ERP5Document_getHateoas.

If the max number of lines of a listbox was set to 0, meaning "no limit set", then ERP5Document_getHateoas would still return a paginated list of 10 results, 10 being
the default set in the parameters of ERP5Document_getHateoas.

It looks like there is a beginning of support for such case in ERP5Document_getHateoas,
with the appearance of code such as "if limit", but the bug comes from the lack of typing in the JS-jIO-JSON-ERP5's HAL interface. In case of a limit set to 0 in the listbox configuration, ERP5
would receive the string "0" which is a non empty string. It would fail the condition and would
be handled like there is a limit, or of 0 - so no result - or of a default limit chosen by the code.