summaryrefslogtreecommitdiff
path: root/addons/web/static/tests/fields/special_fields.js
AgeCommit message (Collapse)Author
2018-10-31[FIX] web: remove debug in timezone_mismatch testAdrien Dieudonne
Before this commit, a blank page was shown when tests were running in /web/tests. closes odoo/odoo#28319
2018-10-29[FIX] web: display of timezone mismatch select widgetLucas Perais (lpe)
On the user's preference, change the timezone to one that is different from the browser. Save the form. Go back to the user's preferences. Before this commit, every timezone was displayed inside the span that contain the warning icon, and leaked everywhere on the form view. This was because of the joint action effects of commits: 86897ca167338ca434e62827fa09f44ddbce324c 4dfabb8f7adde06a7936502af61534c9958ed4f7 Which provoked the field to be re-rendered in edit mode, but with an $el on which a span was added. `<option/>` elements were then added to both `<select>` and `<span>` This did not happen before v12.0 After this commit, there is no display glitch OPW 1895088 closes odoo/odoo#28108
2018-08-13[IMP] base, *: use a many2one for the company report layoutChristophe Matthieu
Before this rev. one could set the report layout on the company using a hardcoded list (background, clean, standard, etc.). Other modules (typically accounting modules) could add options in this list. The used template was built on the layout key. Now, the layout is a many2one field to a newly created model `report.layout`, which is linked to a view with the layout architecture. This gives more control to customize reports and create a new layout (without creating a python module that extend the layout selection).
2017-05-04[FIX] web: unable to open User FormView from SettingsChristophe Matthieu
Uncaught TypeError: Cannot read property 'split' of undefined. Crash when the value of widget 'timezone_mismatch' is false in form view.
2017-04-28[FIX] web: FieldTimezoneMismatch does not workChristophe Matthieu
The FieldTimezoneMismatch was redone, but an error was done after the last code review. With this commit, we fix the mistake (a function is properly called) and improve the test to make sure we catch such a regression later.
2017-04-19[IMP] web: add timezone_mismatch field widgetChristophe Matthieu
* display a warning when the timezone offset is not the same of the browser timezone offset * if different, display the time in the selected timezone