The media modal's document tab has cells with icons and filenames. If the filename was too long, it would overflow its cell, which caused an ugly design glitch. This ensures an ellipsis on the filename when it is too long. closes odoo/odoo#69977 X-original-commit: 8a4f4bf04bd5e5f9cf827273ea27a189a43c2515 Signed-off-by: Quentin Smetz (qsm) <qsm@odoo.com>
Commit [1] fixed visual bugs which occurred using the text tools but missed the fact that the tools were shrunk to a very small height when the editor panel was filled with a lot of snippet options. [1]: https://github.com/odoo/odoo/commit/a99ed0f4a261fba44b31e3fe7a5840d81727b6d0 Fixes https://github.com/odoo/odoo/issues/69097 closes odoo/odoo#69200 Signed-off-by: Quentin Smetz (qsm) <qsm@odoo.com>
The user was not able to select some options of the color and style pickers on the website editor. The menus were displayed either at the top, behind the top actions bar, or overflowing the bottom of the page on some small screens. The solution was to display the widget dropdown menus below the options (remove the transform that was displaying them at the top), and make the container scrollable with overflow-y and a flex display. Part of https://github.com/odoo/odoo/pull/65575 task-2446852
Previously, when quality options were not available, the option would simply not be displayed. User feedback suggests that this is confusing, as for example, in the case of modifying the image in a t-field, quality options would not be available when starting the editor, but would become available when picking the image again in the media-dialog. Some leftover code allowed to display a warning about why the quality options were not available in the case where the image is not local to the database. This warning has been adapted to display a more informative message about why quality options are not available, as well as suggest a solution: - External image => download the image and upload it in odoo - t-field => "You need to choose this image again in the media-dialog or reupload it to have access to quality options" - Images that are in an unsupported format (anything other than PNG or JPEG) => short explanation that quality options are only available on PNG and JPEG images. task-2466819 part of odoo/odoo#66732
Styles for the hex and rgba inputs from the color picker were modified on directly from the web module, which means that for a specification concerning only the frontend colorpicker, the backend colorpicker was also changed. This commit reverts the changes that were made and only applies the new style for the website editor. Related to https://github.com/odoo/odoo/pull/65249 closes odoo/odoo#67156 Signed-off-by: Quentin Smetz (qsm) <qsm@odoo.com>
Depdending on situation several fixes (f885202, fc8e446) leads to issue in small screen size: - in iframe editor with without snippets => the width of the content is decreased of several times the sidebar that is not shown - in editor with sidebar => the content gets behind the sidebar With this changeset we remove part of the above commits which seem to fix both issue. note: this also fixes that the mass mailing content applied CSS should not depend on screen size, or what is send would differ dependin on which screen size clicked on SAVE (on last inlining of CSS). opw-2426400 closes odoo/odoo#66074 Signed-off-by: Nicolas Lempereur (nle) <nle@odoo.com>
In ff81fa479 there was some refactoring for change of structure on frontend, but for the iframe editor (eg. mass mailing), this caused that the top edition bar was over the content. opw-2426400 closes odoo/odoo#66068 Signed-off-by: Nicolas Lempereur (nle) <nle@odoo.com>
Before this commit, it was not possible to center a button using the editor option 'align center'. It is because, using document.execCommand(), the Chrome browser doesnt want apply 'text-align: center' on nodes with centered children. And the buttons have the boostrap class '.btn' which adds text-align: center. So the hack here is disabling the text-align property from the '.btn' class during the execution of document.execCommand(). task-2423935 closes odoo/odoo#65544 X-original-commit: d4f38c344360713287eed22872614f46dec7e0f6 Signed-off-by: Quentin Smetz (qsm) <qsm@odoo.com>
*: web_editor Users can choose one of their color combination to apply on the header. If they then choose to make the header transparent over the content for a specific page, the color of buttons & other components in the header should be reset to the default website color combination's colors as the header component are now appearing over the default content. Part of https://github.com/odoo/odoo/pull/65139
Summernote uses execCommand and, worth, obsolete queryCommandState function to customize the edited content. Here we try to hack the function to solve some problems by making the DOM and style easier to understand for the base functions for the duration of their executions. This won't obviously solves all problems but this is an improvement while waiting for the new Odoo editor coming in future versions. The original problem this solves is handling bold text in blog posts. Posts are using font-weight: 300 which is enough to confuse summernote. Hitting bold on a selected paragraph wraps its content in a <b> tag but hitting bold again does nothing... having a <b> rendered as fw-400 is enough to break it. What this commit does is: before any execCommand or queryCommandState being used to modify the DOM or retrieve its state, the whole DOM is forced to fw-400 and <b> elements to fw-700. This also solves issues in some base snippets. closes odoo/odoo#64472 X-original-commit: 424d9661c5657cbcf10ce40acb94a7a200c2a48b Signed-off-by: Quentin Smetz (qsm) <qsm@odoo.com>