| Age | Commit message (Collapse) | Author |
|
This is a simple renaming without adaptation.
|
|
Before this rev., the datepicker could only be opened by clicking
on the input, not on its caret.
OPW 1836520
|
|
Following commit 3741603495532e218b66f3cfa0272e4536f1cf2c:
Datepickers are indeed able to overflow their parent which scrolls.
However, they were not put above modals anymore.
|
|
Due to the library algorithm to place the datetimepicker,
the div containing the input was no longer relative so the caret was misplaced.
Put back the position relative and place the datetimepicker relative to the input.
|
|
The library needs to have a 'relative' positioned parent to place
the datetimepicker correctly.
We don't do that in the template
anymore because it was not working in all the cases.
The template which instantiates the datepicker should define
a parent in position 'relative'.
|
|
from 3.0.3 to 4.17.42
|
|
Avoid duplicating web addon in enterprise by extracting a common basis.
Enterprise features stay in enterprise, but use that common basis.
Mainly:
- JS refactoring and linting
- Conversion of .sass into .less split into multiple files
- Templates cleaning and DOM simplification
- Re-generation of web.pot, and update of .po files
|