Before this commit, if a theme wanted to define a main font for their
theme and let the "headings", "navbar" and "buttons" ones use the same
they had to add this in their map:
```
'font': XXX,
'headings-font': null,
'navbar-font': null,
'button-font': null,
```
Indeed, without setting the "null" values, those font would use YYY
which is the first font defined in the theme config, which might be
different from XXX. And if forcing XXX 4 times, like most themes do at
the moment, if the user wanted to change them all, he had to change the
4 ones instead of the main one.
Now, only the 'font' value use the first font defined in the theme
config if not explicitly set. So forcing the null values is not
necessary, it will be the default behavior.
The advantage is thus also functional, as most theme forced all their 4
fonts so changing the main one did not change the others.
task-2993054
closesodoo/design-themes#593
X-original-commit: fc64bce81e
Related: odoo/odoo#101068
Signed-off-by: Romain Derie (rde) <rde@odoo.com>
Signed-off-by: Quentin Smetz (qsm) <qsm@odoo.com>
> Media query mixins parameters have changed for a more logical approach
> media-breakpoint-down() uses the breakpoint itself instead of the next
> breakpoint (e.g., media-breakpoint-down(lg) instead of
> media-breakpoint-down(md) targets viewports smaller than lg).
> Similarly, the second parameter in media-breakpoint-between() also
> uses the breakpoint itself instead of the next breakpoint (e.g.,
> media-between(sm, lg) instead of media-breakpoint-between(sm, md)
> targets viewports between sm and lg).
https://getbootstrap.com/docs/5.1/migration/#sass
Task ID: 2766483
Part-of: odoo/design-themes#580
See [1], `enable_view()` is now in charge of disabling the already possibly
existing template header (and/or footer).
Disabling `website.template_header_default` was not enough, any of the other
template could have been selected by the user before updating the theme.
Note that when installing a theme the first time on a website, the error won't
occur as `_reset_default_config()` will be called through `_theme_remove()`.
[1]: https://github.com/odoo/odoo/pull/81181
Fixes https://github.com/odoo/upgrade/pull/3048
task-2593407
opw-2680866
opw-2685951
opw-2685124
opw-2679040
closesodoo/design-themes#548
X-original-commit: 9a289ea574
Related: odoo/odoo#81953
Signed-off-by: Romain Derie (rde) <rde@odoo.com>
Before this commit:
- The assets were not enabled or disabled when installing themes because
we searched for assets with the "key" field instead of the "name" field.
- The "Ripple Effect" was not correctly installed on several themes.
Because the variable and the assets were not both activated. Even if the
variable is not used, it is still necessary for the proper functioning
of the option (e.g. _computeWidgetState).
task-2686370
closesodoo/design-themes#546
X-original-commit: 77b2b97f3d
Related: odoo/odoo#81833
Signed-off-by: Quentin Smetz (qsm) <qsm@odoo.com>
In Safari (14+) the CSS workaround to make block "readable" over any bg
is broken. By replacing the current CSS workaround by an appropriate
SVG filter in each themes svg, the problem will be fixed.
This commit will add the svg filter.
task-2667028
closesodoo/design-themes#538
X-original-commit: 545cf002ea
Related: odoo/odoo#81190
Signed-off-by: Quentin Smetz (qsm) <qsm@odoo.com>
This commit injects for each theme a "preferred" palette into the
website's UI palette list ("Theme" tab).
It also removes '$o-palette-priority-prefix' overrides, letting website
handling the palettes order.
task-2656337
closesodoo/design-themes#514
X-original-commit: 0539787e23
Related: odoo/odoo#77857
Signed-off-by: Quentin Smetz (qsm) <qsm@odoo.com>
This commit updates the theme to improve the design with new colors, new
pictures and new snippet customizations.
task-2580170
X-original-commit: 46a1d66d96
Part-of: odoo/design-themes#501
This commit changes the bg-200 static color that some snippets were
using, for the second theme color so that blocks backgrounds connect
well together.
task-2542318
closesodoo/design-themes#15
Related: odoo/odoo#71426
Signed-off-by: Quentin Smetz (qsm) <qsm@odoo.com>
Instead now use another custom mapping for the default colors of the
shapes which are used for the default homepage. This allows for the
built page to work with any color palette (especially useful for built
pages in the new configurator) and to handle footer/header connection.
Also change some shapes and default background colors to match what
the preview wanted directly (instead of relying on user asked change as
that would not be handled when generating the page automatically with
the configurator).
Part of https://github.com/odoo/design-themes/pull/2
task-2491890
closesodoo/design-themes#12closesodoo/design-themes#14
Related: odoo/odoo#71665
Related: odoo/odoo#71768
X-original-commit: 845b969555
Signed-off-by: Quentin Smetz (qsm) <qsm@odoo.com>
Benoit Socias