jQuery's *focus* method must *not* be used: it triggers the blur and
focus events in the wrong order (and potentially more than once),
breaking the focus handling of the o2m editable list and making it
essentially unusable.
The DOM method behaves correctly, triggers the blur first and the
focus second in a different runloop frame (thus it's possible to bind
on blur, wait a set time and execute the actual blurring iif no focus
event has been seen within the form).
bzr revid: xmo@openerp.com-20121211145652-y63a0ny0gmoiozhn
Editable list was losing value when switching to other row from edited
cell (edit, tab-to-next-fiend then change record worked).
When changing row (by clicking on an other row or pressing up/down),
the list view simply request saving the current form and — once that
is done — switches the form to the new row.
The issue is in what happens *during* form-saving: for most text-based
fields (e.g. CharField-like) the field returns its internal
value. Said internal value was only synchronized when the internal
form control (input or textarea) fired the ``change`` event... and the
change event only fires *after blurring* (leaving) the current
field. So the form saving (and thus the retrieval of field values)
occured before the field could sync its internal value with the one
entered by the user.
Added a bunch of commit_value override to perform this synchronization
right before the field's value is requested.
Also removed an extraneous trailing comma in an array, and removed 2
useless temp storage (unused variables beyond their assignment).
bzr revid: xmo@openerp.com-20121210143808-wt4jmi4x0pg85xb8
these events are used by the autocompletion widget internally, if they
bubble upwards they also get handled by the list view which interprets
them as going up/down the list.
Prevent the latter by suppressing bubbling of these events.
bzr revid: xmo@openerp.com-20121210112203-3mry0pvecri0pv9o
The problem occured when opening a form view containing a m2m_kanban
from a kanban view using an Edit button.
Eg: when opening an existing project from project kanban view using
the dropdown item "Project Settings", no "Add" button appears in
the project Team tab.
bzr revid: fme@openerp.com-20121126102533-ak96lhsxbfx8io7n
Since revision 1517, when using the sidebar from a form view, it merged all the fields of the form view in the context of the action.
It was modified to avoid that context pollution, now it only uses those fields to evaluate the context of that action. So it allows
specifying contexts like "{'invoice_id': invoice_id}", but invoice_id will not be propagated any more to the new action context if not
explicitely specified.
bzr revid: nicolas.vanhoren@openerp.com-20121120100620-ig4e02uctysk7oj8
move special case in o2m listview to main editable and expand to
correctly fit edition cases, not just work in case of creation
issue: if a row being edited is deleted in an o2m, the form will be
blurred and try cancelling/saving the edition and reloading the row,
but this will only happen *after* the record/row/whatever has been
"deleted" and (amongst other things) removed from the buffered o2m
cache, leading to a tentative read on the server side (usually with a
local id which doesn't even make sense) and thus an error.
Intercept the deletion signal to cancel the edition immediately and
only let the deletion through after the edition has successfully been
canceled.
bzr revid: xmo@openerp.com-20121116164416-8kr39t6jtqy2s3jc
niv-openerp
Christophe Matthieu
Xavier Morel
Fabien Meghazi
Christophe Simonis
tsabi
tsabi
Tejas Tank