diff options
| author | qsm-odoo <qsm@odoo.com> | 2018-09-12 14:16:52 +0200 |
|---|---|---|
| committer | qsm-odoo <qsm@odoo.com> | 2018-09-12 17:54:42 +0200 |
| commit | 4a7623fec1a7a4c5a20cc4665396a6d89e6933d2 (patch) | |
| tree | 8cb03416568dfb61f3a3f352a3130c531f312e24 /addons/web_editor/static/src/xml/editor.xml | |
| parent | 611b42409e426f64948499d92a95f5621e053dce (diff) | |
[FIX] portal, website: allow to use wide brand logo
When the user chose a very wide logo for the website navbar, it
overflew over the menu items (making the "+" feature look broken).
This in fact occurs since commit https://github.com/odoo/odoo/commit/4bc79da943c71e762e1f6dedbe3a641042bfef3f.
Its goal was to avoid top menu flickering due to that "+" button
feature. To do that, menu items were hidden with an height of 0 during
loading, then, once the correct number of items needed for the "+"
feature was computed, they were made visible to the user. Another
problem was due to the logo image loading. When it is not loaded yet, we
cannot properly compute the number of items which is needed. To solve
that problem, we fixed the size of the image container instead of
setting the height of the image itself.
But fixing the size of the image container only created a new bug: very
wide logos overflow this container. This commit solves all the problems:
1) The height of the image is set to be equal to the navbar links.
2) The height of the navbar is not forced, meaning that if the user
decides to change the height of its logo to go against (1),
everything will be adapted accordingly.
3) During loading, the menu items are still 0px tall, hidden and made
visible once the "+" feature is enabled.
4) The "+" feature is only enabled once all the navbar images have been
successfully loaded.
task-1878245
Diffstat (limited to 'addons/web_editor/static/src/xml/editor.xml')
0 files changed, 0 insertions, 0 deletions
