auto=True reports are looked up in the database for each rendering, so they do
no have to be in the report registry any longer.
auto=False reports will register themselves but at this point
they can be updated to use the new `parser` XML attribute.
bzr revid: vmt@openerp.com-20130322153955-s6nyux2pyez6c01w
Their changes are not propagated to other processes in a
multi-process setting.
It means that now calling these on auto=False webkit reports
will not have the desired effect. But really they can be updated
to use the new XML parser attribute, and the create/write/unlink
features should be on the base class, not in this module.
bzr revid: vmt@openerp.com-20130322152741-zdmwga2u7uqsv2c3
It was wrong: only the auto=True reports should have been registered
by that method to respect the framework behavior.
And those auto=True reports should not be registered anymore:
the framework will always look them up in the database.
bzr revid: vmt@openerp.com-20130322152356-n66b7igi68pv78ip
with a message_id already existing in database. Indeed loops can occur when
openerp send notification emails to partners having an email address
matching an alias. The mail was routed in the same thread, leading to
further notification emails sent, causing an email loop.
Before trying to find possible routes, check that the incoming email's
message_id is not already present in mail.message table.
If it is the case, return False.
Parsing of the message has been moved before routing, to avoid looking
for routes for emails we will discard.
bzr revid: tde@openerp.com-20130322142916-0q3epz7dpgkyzuj0
Before trying to find possible routes, check that the incoming email's
message_id is not already present in mail.message table.
If it is the case, return False.
Parsing of the message has been moved before routing, to avoid looking
for routes for emails we will discard.
Tests have been added and updated.
bzr revid: tde@openerp.com-20130322124809-ven2p5kxpqfjqxb5
The focus() of AbstractFormField should return false if field
is not focusable otherwise it breaks FormView's#autofocus()
Also added checks of existance of the element to focus.
Those errors makes it harder to find other bugs
bzr revid: fme@openerp.com-20130321220636-1pja2ahsdstyl8kz
@include text-to-icon makes the text invisible (and adds an icon), but
some platform apparently don't apply the text's transparency (or
visibility) to its shadow, leading to the invisible text's shadow
still being noticeably visible (an interesting literary idea, an
"invisible" man who still casts a shadow?) as if the text had not been
erased. Furthermore, combined with the 1px font size it made the text
look like some sort of screen smudge or glitch.
Fix by erasing the text-shadow as well as the text.
lp bug: https://launchpad.net/bugs/1158304 fixed
bzr revid: xmo@openerp.com-20130321164741-iakau7g1kfq2mqu4
On click on a filter in the drawer, FilterGroup would just match the
offset of the filter in the group's DOM with an index in the internal
#filters array.
This worked until invisible fields, and then again only for filters
*preceded* by an invisible sibling in the same group: invisible
filters are not rendered in the DOM, so the indexes would get out of
sync.
Fix by using explicit indexes stored in a filter's @data-index and
using that to get the filter object/node.
An alternative fix (but hackier I think): instead of not rendering
invisible filters, render them with display: none. Remains an option
in the future if needed...
lp bug: https://launchpad.net/bugs/1157125 fixed
bzr revid: xmo@openerp.com-20130321155123-211iht7c6zme712e
Vo Minh Thu