As mode is not always filled, we must compare only if view_ids is empty and we
must use the default value as fall-back.
The limit is a local parameter that should not be forced when opening an URL.
The screen context may be modified thanks to the context model, we must compare
the current context of the screen instead of the initial one.
issue8977
review272751003
We sent an order to the client for action and xxx2Many so its screen has
always a default order set.
To position a new record on non editable tree, we use the order of the 'id'
column if presents.
issue8880
review276501003
Otherwise this trigger a display before the focus out of the previously focused
widget. Such that the previous widget may loose its data.
So we prevent datetimepicker to set a moment and such that it behaves like
tryton.
issue8921
review266581003
The jQuery ':visible' test does not work because the content is not always
fully rendered.
As the jQuery selector is expensive, it is better to keep those cell visible
even on small screens as long as CSS does not provide a proper selector for
this case.
issue8919
review252771003
Re-construct the tree looses the cursor, the expand state and the editable
cell. Until now, we always re-constructed the tree on display because there was
no simple test like the size for the list.
Now we compare the flat list of records following the expanded row. We
re-construct the table only if they are different.
issue8854
review264671003
issue8571 introduced the validate attribute but the test against validate
record is wrong as it stop processing when the record is actually valid.
issue8886
review252731002
When there is a large amount of all day events, the agenda views do not display
the time table because it computes a height of 0 (probably to keep the aspect
ratio).
issue8877
review260611002
The model of the wizard can be a children of the main model. So we must compare
against the model of the menu and always fall-back to the current tab screen.
issue8837
review276371003
The value is rounded in apply_factor is needed or set to default value if it is
not a number.
This prevents the user from losing its invalid input.
issue8841
review250311002
In order to have correct overflow ellipsis, we must stop to use table to align
affix inside a cell. Instead we use flexblox layout to expand the widget and
align the affixes.
Also as now content will be ellipsis, we must provide a title to the buttons.
issue8762
review268231002
This avoids to use negative margin to keep row heigh constant.
And we display the button as block on responsive tree to make it easier to
click on.
issue8761
review286171004
The result of Math.pow may have rounding issue (especially on Chrome) so we
must round it otherwise the validation of the input may fail.
issue8707
review258301002
By default an export is only available for his creator and administrators.
We add a list of groups that are allowed to read and a second subset of groups
that are allowed to modify it.
issue8695
review252331002
All the rows must be expanded to be able to set the focus, which means waiting
the promises. But also the current record must be selected in the display and
the expanded rows must have expander updated.
issue8672
review252221002
During the initialization of the widget, the view may not yet have a proper
record. But update_img access the record of the view.
Also it is safer for list-form to define the _record before calling super in
case there is an access to record attribute.
issue8616
review285981002
Cédric Krier