..cher
Defines dataset directly on website elements such that it can be
overridden by other modules if necessary.
This was done due to the override in the `test_themes` module completely
overriding all attributes of the website_switcher's dropdown items.
Runbot Error 106501
closesodoo/design-themes#1027
X-original-commit: c5f4e1c414
Related: odoo/odoo#190475
Signed-off-by: William Braeckman (wbr) <wbr@odoo.com>
*: anelusia, anelusia, enark, kiddo, loftspace, notes
- Install Website e-commerce.
- Select the "Kea" theme for your website.
- Go to the "/shop" page.
- Click on "Desks" category to go to the "/shop/category/desks-1" page.
- Click on edit to enter edit mode.
- Click on the "theme" tab.
- Change the website background color to "black".
- Bug: The breadcrumb has an ugly white background instead of no
background color, as in the "default" theme. Also, the "active"
breadcrumb item is hidden due to white text on a white background.
This commit removes the white background from the breadcrumb for all
themes that use it. This ensures the same appearance as other themes.
opw-4232082
closesodoo/design-themes#1016
X-original-commit: fe91239586
Signed-off-by: Serge Bayet (seba) <seba@odoo.com>
In some theme customizations, some replaced images do not have the usual
image classes `img img-fluid mx-auto` anymore. The `img-fluid` one is
needed for grid images in mobile view, as they are overflowing without
it.
This commit adds these missing classes on the identified problematic
images.
closesodoo/design-themes#998
X-original-commit: c5adf9a903
Related: odoo/odoo#185404
Signed-off-by: Quentin Smetz (qsm) <qsm@odoo.com>
In order to simplify the tours API, it was decided to remove the
extra_trigger key from the steps.
To check that an element is in the DOM, simply create a step with
a trigger.
task~3974087
closesodoo/design-themes#816
Related: odoo/odoo#171309
Signed-off-by: Quentin Smetz (qsm) <qsm@odoo.com>
For each theme, there are files redefining the different website SCSS
variables, in order for the color palettes, fonts, buttons,... to have
the styles defined by them. These redefinitions are also used by the
"Theme Options", to show the current values in the different widgets.
In order for the primary buttons to be "outlined", the "Enark" theme set
the `btn-primary-outline` variable to `'true'`. However, this value
should be a boolean instead of a string. Indeed, since the option does
not recognize the string value, the "Buttons Primary Style" widget
therefore shows a "/" instead of "Outline", which is not correct.
This commit fixes this by setting a boolean value.
opw-3957157
closesodoo/design-themes#814
X-original-commit: 14ff983da2
Signed-off-by: Quentin Smetz (qsm) <qsm@odoo.com>
Currently, in tour_compiler, to check that an element is actually
present in the DOM in a step, there are 2 possibilities.
- `isCheck: true` => Checks that the element is in the DOM.
The latter can be disabled.
- `run() {}` => Checks that the element is in the DOM (because this
is what is done by default). However, if the element is disabled,
the step will be aborted.
In the codebase, we can see a lot of `run() {} //it's a check` and
`isCheck:true`. However, the behavior is not exactly the same.
What's more, there are 2 ways to do "the same thing".
In order to clarify the turns API, it was decided to no longer put an
action (step.run) by default. (Previously, the default action was
the "click" action).
From then on, it is no longer necessary to stipulate
`step.isCheck: true` nor `run() {}`.
The corollary is that now, you must explicitly write `run: click`, if
you want the click action to be triggered on the target.
This commit sets the stage for making this change.
closesodoo/design-themes#801
Related: odoo/odoo#167743
Related: odoo/enterprise#63711
Signed-off-by: Julien Mougenot (jum) <jum@odoo.com>
Odoo Translation Bot