[MERGE] forward port branch saas-12.4 up to cda4f3c308c

2 files changed, 16 insertions, 2 deletions

diff --git a/doc/reference/qweb.rst b/doc/reference/qweb.rst
index a4a5b3769a4..8e984f68a73 100644
--- a/doc/reference/qweb.rst
+++ b/doc/reference/qweb.rst
@@ -491,6 +491,11 @@ on the extended template to select *context nodes* to which the specified
     the node's body replaces the context node's children
 ``replace``
     the node's body is used to replace the context node itself
+``attributes``
+    the nodes's body should be any number of ``attribute`` elements,
+    each with a ``name`` attribute and some textual content, the named
+    attribute of the context node will be set to the specified value
+    (either replaced if it already existed or added if not)
 No operation
     if no ``t-operation`` is specified, the template body is interpreted as
     javascript code and executed with the context node as ``this``
diff --git a/doc/reference/views.rst b/doc/reference/views.rst
index 8b632bba228..09c6ed55c5e 100644
--- a/doc/reference/views.rst
+++ b/doc/reference/views.rst
@@ -332,12 +332,21 @@ Possible children elements of the list view are:
     ``width_factor`` (for ``editable``)
         the column relative width (as the layout is fixed)
     ``width`` (for ``editable``)
-        the column width (as the layout is fixed)
+        the column width (as the layout is fixed). It is a string describing the
+        width css property, such as '100px'.
 
     .. note:: if the list view is ``editable``, any field attribute from the
               :ref:`form view <reference/views/form>` is also valid and will
               be used when setting up the inline form view
 
+    .. note:: When a list view is grouped, numeric fields are aggregated and
+              displayed for each group.  Also, if there are too many records in
+              a group, a pager will appear on the right of the group row. For
+              this reason, it is not a good practice to have a numeric field in
+              the last column, when the list view is in a situation where it can
+              be grouped (it is however fine for x2manys field in a form view:
+              they cannot be grouped).
+
 ``groupby``
   defines custom headers (with buttons) for the current view when grouping
   records on many2one fields. It is also possible to add `field`, inside the
@@ -346,7 +355,7 @@ Possible children elements of the list view are:
 
   ``name``
       the name of a many2one field (on the current model). Custom header will be
-      displayed when grouping the view on this field name (only for first level).
+      displayed when grouping the view on this field name.
 
   .. code-block:: xml