The wiggling effect of the edit button when clicking on the form
(hinting that to change the form you should edit it) could happen
several times.
With 85d1e76 there was also a visual deffect on the Edit button when the
wiggle happened several times, because bounce are stacked but the CSS
class was removed after the first bounce was removed.
Use case to reproduce:
- Create a product with a BOM needing one component tracked by SN
- Create a MO for this product with 2 to produce
- Produce 1
- Produce the other -> 2 lines and a wrong lot proposed
This happens when the quantity to consume is equal to 0
or if the qty_done on a move_line is equal to the reserved
quantity.
This commit change the condition after the float_compare in
order to take into account the equal comparison.
Since the function in order to generate a MO is usefull
for mrp test. It could be great if we could use it in
every test.
This commit also add 3 arguments in order to modify the
quantity needed for each product.
This commit introduces a new way to hide a column in a x2m list view.
The attribute 'tree_invisible' can be add in the field attrs in the x2m
view definition. This attribute can use the 'parent' key to make a reference
to the parent record (e.g. 'parent.id').
Make it easier to take advantage of subqueries whenever possible.
Also remove some weird semantics of the operator `not in`: searching with the
domain `[(F, 'not in', [])]` was returning the records with relations, instead
of all the records. The new semantics makes `[(F, 'not in', ids)]` equivalent
to the complement of `[(F, 'in', ids)]` in all cases.
Rev. 2728fe1 introduced an attempt of restoring the focus on the
currently focused field in an x2many list after an onchange
returned, and the list has been updated. However, it was often
wrong (e.g. leaving a field by pressing tab/shift+tab, clicking on
another field...) and reset the focus on an unexpected field.
In addition to fixing this issue, this rev. also unifies the helper
functions to get and set the cursor positions in an input or
textarea, as they were duplicated between mail and web.
The `isMobile` variable was defined at the right place (`config.device`)
but was set at the wrong place (`config`).
Thank you for making me author of all the `isMobile` lines by
the way... :)
This reverts commit b94939377a.
The commit was breaking most of the backend checkboxes trying to fix a
frontend one.
On top of the revert, this commit adds frontend-only style to fix the
frontend checkboxes.
Before this commit, when Sending the receipt by email (payments) the full partner form was displayed in case the partner didn't have an email set.
Now, just like invoices, the simpler version is displayed
The save on the frontend worked, but there was no feedback that it
worked if the identifier of the file currently edited broke a jQuery
attribute selector value (eg. /test.less breaks it).
When creating an acitivity generating a calendar event, if
the model is not crm.lead (ex: sale.order), the default_get
will crash since no value for res_model_id is given.
Purpose
=======
If you create a product template with only the name set, the system proposes to update translations for all the translatable fields, even if no value is set for a field.
The google 'video.google.com/get_player' URL seems to be deprecated so
the URL used by website_slides had to be updated.
Also when switching a slide URL from a drive URL to a youtube URL, odoo
still kept thinking it was a drive URL.
opw-773984
In mobile mode, dropdown-menus are working with a dropdown backdrop for
mobile compatibility. As the z-index of kanban dropdown-menus were now
forced to 1 for no good reason, those appeared under the backdrop and
were thus not working.
Before this fix, trying to create a column in a kanban view where there
were progressbars was opening a traceback. This was because the newly
create column is made from data which are guessed in the client (no RPC
is done), so this guess had to be adapted to progressbars.
Previously a user was only able to scrap reserved product
(products that have a stock move line associated on the picking).
With this commit the user can scrap any product that has a move
on the picking.
Previously editing a done move line only update
the quants to the right location. However the stock.scrap
related object has not its qty updated.
This commit modify the write of stock move line in order
to also modify the stock scrap object to the correct quantity
When the user scrap a product in a picking.
The moves to proccess are moved to a back order and
the current picking only contains the scrap move.
It happens because scrap use action done on the scrap
move and action done process the given move and put the
other in a back order.
This commit add a condition on back order creation in
order to not do it if it comes from a scap.
Moises Lopez - https://www.vauxoo.com/