Remove fixed width for kanban records in .o_kanban_mobile (in grouped
view the records overflowed their columns).
Note: this class seems useless and wrongly used by templates. This
should be removed in master (remove the class from templates and
include its less rules in all kanban records for specific classes).
If the kanban view is loading grouped records, the dataset of the view
itself is the concatenation of the dataset of each groups.
But when using "Load more..." on a column, these records are not added
in the view dataset which is thus desynchronised. This could lead to an
error down the road.
closes#10156
opw-659016
If a kanban tile is moved to another column, in case of failure it
would stay in that column giving the false idea that it somewhat worked.
This commit refresh the kanban view in such an instance.
closes#9837
first half of opw-657863
When the kanban view is grouped, it did not correctly set the ids of the
dataset. Consequently, the user could find himself in some weird
situation, such as having X issues visible in a kanban view (typically
grouped with a custom filter), then clicking on it, and arriving in a
form view with Y issues, and X != Y.
In sales dashboard, when there is no sales team, the no content message is displayed next to the dashboard.
The class o_kanban_ungrouped adds style to avoid this problem.
Credits to @qsm-odoo.
When creating a team.user record, there was an error to generate an url
for the image because the attribute "__last_update" didn't exist
on the record.
opw:653725
When several accesskey with the same key, are defined on elements, the
last one (even if not displayed) is the one which will be actioned and
the key sequence is pressed.
This caused an issue since the "Pager" template is shared between all
elements, even the x2many relational widgets.
Also there was shortcut for Create/Save/Discard on the form view, but
those shortcuts should also be enabled in the list and kanban view.
closes#9267
opw-652888
Coming from hr_recruitment, where kanban_state is displayed, but without the customization
Also, remove lingering options in view, and missing fields for project_issue
- Change the widget behavior from asynchronous to asynchronous, by adding 3 related fields
on the project.task model, which are the custom labels defined for the stage
- Instead of making a rpc call, we are taking directly the labels on the parent for the kanban view,
or on the view datarecord for the form view
- There are now 2 templates for the kanban view or the form view
- The development has been backported in the community version
- The options attribute has been removed on the project_view.xml file for the kanban_state field
The hightlight element when a tip is clicked was placed over a white
rectangle. This induced a problem if the element was itself white.
Also the dimension of the helper were badly computed.
+ remove specific tip style in kanban view
Contexts in formview which contained parent.[some_field] were not able
to be evaluated when creating a record from a many2many_kanban because
the parent view was not given to the creation dialog.
There are several problems with kanban record :
* Ideally they should not use row/col as the grid gutter is too big for
small cards like them
* Some template use rows but kanban record padding is not the same as
a container (and so rows are overflowing the record)
This does not induces a serious problem in desktop version because there
is enough space aroung the records to not have a visual problem.
However, this induces an horizontal scrollbar in mobile as the records
are full width in this mode.
Some solutions were possible :
* Change all record padding to be equal to the bootstrap container
padding -> not chosen because this would impact every record and the
gutter will be too big and make many records ugly
* Overriden inside-record rows and cols to have a smaller gutter
-> not chosen because this will add ugly rules alongside impacting
every record
The chosen solution is to increase the horizontal record padding in
mobile only. This will even align the record content with control
panel content.
How great is it to get Odoo (almost) 9.0 (almost) translated?
Clean .tx/config file
Regenerate .pot files
Fetch current translations from Transifex (10% completion)
In all browsers the ``focus/blur`` event is triggered before a button's
``click`` (it's actually triggered by mousedown).
Column and record quick-creates discard the form on blur but still want
to create the column/record when the "Add" button is clicked. This was
implementing with a fixed debounce/time-delay on the blur handler,
however the exact delay between blur and click dispatch are browser,
environment and possibly load-dependent (on my system unloaded, 10ms is
sufficient in webkit but firefox requires at least 50, a user keeping
the mouse button pressed for some time would increase that delay).
The proper way to handle this is to suppress the ``focus/blur`` event
from the relevant button entirely by preventing the browser's default
mousedown handler.
Do that for both column and record quick-creates, and remove
time-delay/debounces.
Also remove manual proxying of ``click`` in kanban column (move to
``events`` object)
Now that most refactoring has been merged
It is better to have red a great work of another culture in translation than never to have read it at all.
― Henry Gratton Doyle
When creating a record from a many2many_kanban, it did not contain all
the data the kanban view asked to render itself. This fix extends the
record data with undefined value for unknown (but asked) data.
* Fix alignement/layout problems since the reintroduction of
bootstrap grid gutter.
* Fix mobile layout problems.
* Fix various Firefox problems.
* Use odoo variables and simplify LESS.
* Use input type="text" instead of input without type.
In chrome, there was a gap at the end of the dashboard because of :
* after/before element in kanban record
* flex items were able to reduce their size
qsm-odoo