summaryrefslogtreecommitdiff
path: root/addons/mail/static/tests/thread_window/basic_thread_window_tests.js
diff options
context:
space:
mode:
authorLucas Perais (lpe) <lpe@odoo.com>2018-11-14 15:45:31 +0000
committerLucas Perais (lpe) <lpe@odoo.com>2018-11-20 10:06:18 +0000
commit462681723b63b5cacb943a2b1f40b26cb1355d83 (patch)
treea09f1bd5cd5771d24e8d31c18faa59db41259440 /addons/mail/static/tests/thread_window/basic_thread_window_tests.js
parent8ccc976c2088bff23071d495f2d74a3ea6a26038 (diff)
[FIX] web: search input date in another timezone
Put the browser in timezone Sao Paulo (Or like West of UTC) Trigger the autocomplete (and the subsequent search) on a date field by writing a date (in the locale format) in the search view Before this commit, the domain sent to the server contained the date as the day **before** the one asked for in the input This is because, the string input is parsed and gives: input = 12/02/2018 When creating the moment object: > since there is no explicit time, moment will interpret it as 12am (midnight) > We force moment to consider the string as being UTC (function: moment.utc()) > the moment contains, as output the time ** 2018-02-12T00:00:00 UTC ** When getting the facet value for making the domain > we call toDate on the moment object, which, according to the browser is UTC and will be converted to the locale timezone before formatting > And the domain will use the date 2018-02-11T22:00:00 Brazil/SaoPaulo which gives the day before the one we asked for After this commit, this issue doesn't arise, because we don't convert the moment into a Date, and we directly format that moment into a string OPW 1903224 closes odoo/odoo#28689
Diffstat (limited to 'addons/mail/static/tests/thread_window/basic_thread_window_tests.js')
0 files changed, 0 insertions, 0 deletions