summaryrefslogtreecommitdiff
path: root/addons/web/static/lib/bootstrap-datetimepicker/src
AgeCommit message (Collapse)Author
2019-01-29[FIX] web: current dateNicolas Martinelli
- Set the OS in a timezone such as the current day is different from the day in UTC (e.g. America/Nome before 10:00 AM or Australia/Melbourne after 3:00 PM) - Open any datepicker - The 'little triangle' indicating the current day is wrongly set (one day before or after) Knowing that Odoo always creates momentjs date and datetime with the `UTC` flag set to `true`, the `bootstrap-datetimepicker` does something which seems inconsistent. First, it retrieves the `viewDate`, and sets it to the beginning of the month and week in: https://github.com/odoo/odoo/blob/1c6c504215f3ef09e6336c92c9d350e87599eaa1/addons/web/static/lib/bootstrap-datetimepicker/src/js/bootstrap-datetimepicker.js#L725 In this part, it is important to note that each `startOf` functions called sets the hours/minutes/seconds to zero. It means that the reference time is changed. Then, it iterates on this newly created date, and determines `today` by comparing it to `getMoment()` in: https://github.com/odoo/odoo/blob/1c6c504215f3ef09e6336c92c9d350e87599eaa1/addons/web/static/lib/bootstrap-datetimepicker/src/js/bootstrap-datetimepicker.js#L748 However, `getMoment()` returns the current date and time, but with the `UTC` flag set to `false`. Therefore, we compare a UTC datetime on which the reference time has been changed to a non-UTC datetime, which fails to give the appropriate current day. There are two approaches to solve this. The first possibility is to change the way Odoo defines momentjs dates and datetimes, maybe by removing the `UTC` flag at creation. This sounds like a bad idea, since other widgets or views (such as the calendar or the pivot view) make use of them. This is likely to introduce a bunch of new issues with TZ in these views. The second approach is patching the library to fit our use. Although we usually don't do such a thing, this allows to specifically solve this use case, and in particular placing the 'small triangle' at the appropriate date without impacting any other part of the system or the library. It can be easily performed by comparing the dates and the months to make it work. opw-1915251 closes odoo/odoo#30538
2017-12-04[FIX] web: datepicker: notify all datetime changesAdrien Dieudonne
Before this fix, there was an issue when you changed the value of a datetime field by editing direclty the input (without using the datepicker popup). If this value was equal to the offset of your timezone, the new value wasn't saved. The problem was that no event was triggered by the 'bootstrap-datetimepicker' lib because it considered that the old datetime and the new datatime were the same... In odoo JS, we always manipulate UTC moment objects and we manually add the timezone offset at rendering (we mainly do that for testing purposes). When the offset is added, calling format() on the moment object doesn't convert the datetime to the browser timezone because it's flagged as being UTC. The datepicker lib creates moment objects in the browser timezone. So comparing the ones it creates with the one given by Odoo is like comparing apples and oranges, and it gives wrong results when the datetimes differ by the exact timezone offset. So in this case, no 'datetime change' is triggered by the lib. We could fix this by wrapping moment objects into some kind of OdooDate class and stop manually adding the timezone offset, but this would involve a refactoring that can only be done in master. Instead, we prefered to patch the lib to ignore the comparison between UTC and non-UTC objects, as this is the safest way we find to fix this issue in stable version.
2017-06-07[FIX] web: restore broken datepicker since lib updateqsm-odoo
There were two main problems with the datepicker since the lib was updated: - it appeared broken in the search view "Filters" menu - it did not overflow the parent which scrolls Indeed, before the update, the datepicker was placed in the <body/>. Now this is a lib option. Unfortunately, the option is broken (I don't know why they broke it since it worked before the lib update...). As the lib does not expose its internal functions, the only found workaround was to patch the lib code itself. opw-745311 opw-745625
2017-01-30[REF] web: update bootstrap-datetimepicker lib and adapt datepicker widgetfwi-odoo
from 3.0.3 to 4.17.42
2014-08-25[FIX] web: update moment and datepicker library also add a controller to ↵Cedric Snauwaert
lazily load locale
2014-08-25[FIX] web: remove old datetimepicker and change by bootstrap datetimepickerCedric Snauwaert