With 3e82c94d we use the timezone in the context to format date
sequences when formatting an ir.sequence.
This commit adds the other missing context when getting a sequence, so
these sequences are also dependant on the timezone.
closes#8351
opw-646487
Barcodes are detected by catching keypresses. When a keypress is not
part of a barcode, it is 'released' by forging a keypress event.
For security reasons, a non-native keypress doesn't trigger the native
input mechanism. So in order to make both barcode-scanning and manual
keypresses work in a field, it is necessary to have a handler listen
to the 'false' keypresses and simulate the native input behaviour.
lxml.HTMLParser detect the content encoding by itself if not specified.
in the issue leading to this fix, content in a mail with u'\xa4'
( ) was transformed intto u'\xc2\xa4' (Â ) since HTMLParser
selected the wrong encoding (latin-1 instead of utf-8 for example).
this commit specify the known encoding and revert 3d00c210f which was
another attempt at this issue.
- GMail caches the images contained in emails
- It seems to take the opportunity to replace `%20` by `+` in the images URLs
- Werkzeug doesn't seem to handle '+' in URL as spaces (at least not as a %20)
(See https://github.com/mitsuhiko/werkzeug/pull/756)
When inserting a fontawesome character/image,
there are spaces in the CSS color,
e.g. `rgb(255, 255, 255)`.
And window.encodeURI, doing its job, encode this as
`rgb(255,%20255,%20255)`
This, in the URL, is supported by Werkzeug.
However, Google changes this to
`rgb(255,+255,+255)`
which is not supported by Werkzeug.
The fontawesome images were therefore not available in
mass mailing sent to GMail addresses.
This revision removes the spaces from the CSS color.
This is not the best fix, but
- We cannot really ask Google to not change %20 by +
- We cannot afford to wait the support of the '+' as spaces in Werkzeug
opw-648456
Would trigger a UnicodeWarning when looking to update ir.model.fields
in _field_create (final loop): the unicode value from the database
would be compared with the str value from the model, the str would
fail to decode triggering the warning and assuming a False test,
probably also triggering an unnecessary database UPDATE.
This one has been settled there for ages
but gives the wrong impression it is only editable in draft and sent state.
Nevertheless readonly=True is not define.
Thus this confusing dict is useless.
Closes#3734
* 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.
The total used to check which delivery.grid.line to apply must be in
the currency of the company because the delivery.grid.line records with
variable == Price are expressed in the currency of the company.
opw:647799
When creating timesheet,
default from-date and to-date are adjusted for user timezone.
Fixes#3627
User timezone considered when assigning attendance records to timesheet
Fixes#3628Closes#3632
Raphael Collet