The refactoring of the wysiwyg editor and 'html' field allows us to move some of the code that was in web_editor but only used in website or in mass_mailing. Some parts are still in web_editor but will be moved at a later time.
Compatibility: rebuilding a correct modal from user database content. Since the first version, the modal is saved in databases directly but has never used a correct structure. While it was working with BS3, it is not with BS4. This was breaking the design and prevented the modal to be able to close. task-1889341 closes odoo/odoo#28589
Purpose behind this commit is to remove font-family from all elements in plaintext theme. So mail receiver will see this mail in default system font. This is inspired by new Gmail and suggested by FP As we want to show system's default font in the mail sent with the basic theme. And so we remove font-family from basic theme while saving. But by doing so in readonly mode is not getting proper font in odoo as we don't having any assets in readonly mail editor. So we added stylesheet just for display purpose.
- Go to Mass Mailing > Configuration > Mail Templates - In the Kanban view, find a template which contains a link (http, mailto, whatever) - Click on the link You are redirected to the link instead of being redirected to the record. opw-706047
Change color #a24689 to #875A7B Commit https://github.com/odoo/enterprise/commit/8ac1c19fac7615fecd51e670f798d13158a4e53c changed the odoo interface violet by changing the main LESS variable but forgot there was many direct occurences in XML/HTML/... (for example for the mobile browser color). Even if it's community the odoo interface violet is used at many places (module description, XML demo data, ...).
* Use the theme class selector as root for the less file -> Allow to style the editor as applied to the body -> Split in editor/color/layout/snippets * Create an assets to contain all mm themes so that the compilation is made by the odoo system, and allow minification and variable sharing between themes -> Remove css files * Reformat the LESS files content
website -> web_editor so that they are available for mass_mailing. To allow setting margins on td elements: As the above mentionned option allows to control the mt and mb classes on the mass mailing items, the problem is that we would ideally want it to be functionnal on td element as they are the main part of a mail. As they don't support margins, there were many options to fix the problem: - Add more JS to place the mt and mb classes on children of td element - Place the option on children of td element and not td element itself but in that case, the width control of td would imply a lot of parent option hierarchy, or the width control had also to be adapted to control children - Control padding instead of margin. This forces to add lots of css rules like pt4 pt8, ... (or td.mt4, td.mt8, ...). The last solution has been chosen. Padding is more supported than margins in mail client anyway and the css rules will be isolated in the mail editor anyway. Using td.mt4 instead of pt4 had the advantage to not require any JS modification.