lp:txerpa-openerp-web

Branch merges

Propose for merging

No branches dependent on this one.

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

4670. By Launchpad Translations on behalf of openerp on 2011-07-23

Launchpad automatic translations update.

4669. By Launchpad Translations on behalf of openerp on 2011-07-20

Launchpad automatic translations update.

4668. By Jay Vora (Serpent Consulting Services) on 2011-07-18

[REVERT] Reverted the revision 4665 <email address hidden>

4667. By Sananaz (Open ERP) on 2011-07-12

[REV] Revert revision 4657.

4666. By Launchpad Translations on behalf of openerp on 2011-07-12

Launchpad automatic translations update.

4665. By Xavier (Open ERP) on 2011-07-11

[FIX] selection widget options updating based on environment content

4664. By Xavier (Open ERP) on 2011-07-11

[FIX] time range imprecision when creating calendar event via drag&drop in day or week mode

4663. By Xavier (Open ERP) on 2011-07-11

[FIX] don't break m2o field values when opening m2o search popup with a preexisting value in the field

Code could blank the visible portion of the m2o field but not the backing ID, leading to a field impossible to edit. Don't blank the visible section if that's not needed, leave old value

4662. By Launchpad Translations on behalf of openerp on 2011-07-09

Launchpad automatic translations update.

4661. By Xavier (Open ERP) on 2011-07-08

[FIX] double-action execution in case of opening action URLs containing spaces

URLs are moved to hash-parameters in order to have navigation between 'pages' (bookmarking as well as forward/back support). The encoding was performed using jQuery.param (encodes the URI provided and sets it as a 'query parameter' with the right name for decoding).

However, it turns out jQuery.param does not merely call 'encodeURIComponent' on the key and the value (separately), it also re-encodes all spaces as '+' (instead of the normal '%20'). This does *not* round-trip through decodeURIComponent.

As a result, we'd store the action URI as 'current uri' and set it as the hash, this would trigger a hashchange which would compare the 'current uri' and the one in the hash (which were set to the same value)... and would find them to be different (due to the '+' encoding of spaces which apparently is not handled by decodeURIComponent), which would lead to a *new* action execution using the +-based action uri. This one would be stored (again), new hashchange triggerd which this time would find the URIs to be identical and would avoid further processing.