We must render such widget to be able to display them when they are no more
readonly. And we must ensure they are loaded and the states is computed when
displayed.
issue8626
review280041002
The issue8312 was to strict by its usage of Group._context as it misses the
context_model, the parent context or the _datetime keys.
Instead we introduce a second type of context which provides the same context
but without the session part.
issue8463
review255831002
On chromium the input does not trigger a change event if the value is the same
(the same file is selected twice).
So we force the null value when the widget is cleared.
issue8513
review265681003
As the optional scrollbar of the treeview will be removed, the dropdown input
may no more be visible. So we must scroll until it is visible.
issue8509
review285581002
We must return the promise of the reload as the button promise to avoid enable
back the button before the screen is fully reloaded.
issue8488
review249661002
When a dialog (form) is validated and show the error message from the browser,
the input number must be visible.
Also we should not store on the model invalid values to get error on client
side instead of the server side.
issue8487
review255661002
The RETURN key should validate and save the current record before creating a
new one.
And UP/DOWN keys should create new record when they are at the end.
issue8485
review251761002
Those calls can be triggered by event like focus-out. So to ensure a correct
order of the flow, we must defer the processing of the result.
issue8482
review273571002
We set a minimal width on the treeview table (min-width on td has an undefined
behavior) by summing the default width of each column.
We add a fake scrollbar on top of the treeview to ensure the user will see that
there are more column to see. The fake scrollbar is a div with the same minimal
width and its parent as the scroll value synchronized with the scroll of the
treeview div.
The minimal widths are removed on extra small screen if the treeview is
responsive because the table has 100% of the width.
To have the minimal width working also on the xxx2Many view inside a form, we
must set a maximum width to the cell. As this width must be expressed in
relative size (not in pixel to support resizing), we express them as
percentage of the width of the viewport. The percentage is computed from the
percentage width already computed but also rated with all the percentage width
of the parent cell. We also remove the maximum percentage of the offcanvas
size. This does not give the exact maximal width but it is close enough to have
a correct behavior no matter the size of the screen.
issue8308
review259411002
Cédric Krier