summaryrefslogtreecommitdiff
path: root/addons/website/static/src/js/editor/snippets.editor.js
AgeCommit message (Collapse)Author
2021-02-15[FIX] website, web_editor: ensure the loader appears on click optionsBenoit Socias
Before this commit the loader did not always get displayed when switching to the options tab. After this commit the loader always gets displayed ASAP when switching to the options tab until the tab is ready and displayed. task-2439295 https://github.com/odoo/odoo/pull/65223 Co-authored-by: Samuel Degueldre <sad@odoo.com>
2021-02-04[FIX] website, web_editor: fix empty parallax snippet not being removedSamuel Degueldre
Previously, when removing all the content of a snippet, that snippet would get automatically deleted. This was not the case for parallax snippets because we previously intended the user to drop the parallax snippet, empty it, and drop other content inside of it. Recently, we added the parallax option on all snippets, rendering the previous workflow obsolete. There is now no longer any reason to keep empty parallax snippets. This commit fixes that. task-2446008 closes odoo/odoo#64907 Signed-off-by: Quentin Smetz (qsm) <qsm@odoo.com>
2020-09-22[IMP] website, *: move page scrollbar to #wrapwrapqsm-odoo
*: web, web_editor, portal, account, website_blog, website_forum This is probably not ideal to move the scrolling behavior out of the html element but this will be needed for the editor to not have a double scrollbar on the right. This is actually also useful for the scrollbar to appear under the purple odoo menu instead of its right. This commit, if to be reverted in the future, however contains many improvements to make the transition easier that should be kept: jQuery and Odoo functions to be able to scrollTo a specific element, get the top scrollable element, check if an element is scrollable, etc. Also, some magic was done: if some code tries to scroll to a specific scroll position via jQuery's scrollTop or animate functions on the html/body element, those will still work as intended (obviously, using the new utils to do that is however recommended). This commit also reviews our scroll behaviors to make them more robust and share the code. Part of https://github.com/odoo/odoo/pull/57975 task-2344227
2020-09-16[IMP] web_editor, website: improve editor loading effectsqsm-odoo
- Share the code for tab switching loading and slow option loading. - Now add a loading effect over the content when the content is changed and a loading effect over the editor panel when the editor panel is being changed Part of https://github.com/odoo/odoo/pull/55614 task-2213114 closes odoo/odoo#55614 Signed-off-by: Quentin Smetz (qsm) <qsm@odoo.com>
2020-08-06[IMP] website, *: review the 'options' tab of editor panelqsm-odoo
*: web_editor This will more probably change again in the future but this is a first step towards a hierarchized 'options' tab for the editor panel. Part of https://github.com/odoo/odoo/pull/55529
2020-07-28[IMP] website, *: move all google map options to left panelqsm-odoo
*: web_editor -> Introduce the we-gpspicker widget and improve the way the gmap lib is loaded (for Odoo / multiple snippets / ...). Part of https://github.com/odoo/odoo/pull/49101 task-2091396
2020-07-14[IMP] web_editor, *: review the editor design CSSqsm-odoo
*: web, mass_mailing, website, website_form, website_sale New CSS design of the editor (step 1/x). This work is unfortunately far from perfect but is a first step towards what we want. In particular, much CSS linked to elements that are meant to be removed/moved in the upcoming weeks was done in a huge rush but will thus hopefully be removed/reviewed before the 14.0 release. As the design is now far more complex including gradients and other "complex" elements, it was also very difficult to keep a design based on css-variable so this system was removed, which means that the editor now appears the same everywhere (backend, frontend, ...). The original goal of this system was to have an adapted style for backend, frontend and website visitors. Unfortunately, the current result was a very good frontend editor design, a not-so-good backend editor design (for mass mailing at least) and a totally unadapted design for the website visitors. Making this perfect will be achievable by loading different assets for those 3 areas and hopefully those assets will only differ by the values of editor scss variables. Part of https://github.com/odoo/odoo/pull/53930 task-2157252
2020-07-13[FIX] web_editor, web: fix traceback with drag & drop when no headerqsm-odoo
Commit [1] introduced the bug by relying on the fact an element with id=top is in the edited DOM. As the website header can be disabled, this induced a crash as soon as the header was indeed disabled. Also, the editor is not meant to edit the website only so we cannot rely at all on the presence of a #top element. [1]: https://github.com/odoo/odoo/commit/6df67a28c2f113572acd4a3db19ab6b1bd37e7da closes odoo/odoo#54409 Signed-off-by: Quentin Smetz (qsm) <qsm@odoo.com>
2020-05-31[IMP] web_editor, website: add loading effect in left panel editorqsm-odoo
The goal is to reduce loadings as much as possible but there will always be some. So that loadings do not appear as bugs and give users some feedback that they are ongoing, this commit adds a loading effect during the loading of some actions. Part of https://github.com/odoo/odoo/pull/52211 Related to task-2197038
2020-05-28[FIX] website, *: review theme tab creation + switchingqsm-odoo
*: web_editor When clicking on the theme tab on an empty page, a scrollbar appeared and stayed. This was because the fake `<theme/>` element was focused and the overlay positioned randomly outside of the page. This commit fixes that by simplifying the code and always hiding the related overlay. This commit also makes sure the onFocus/onBlur method of the theme options are called consistently, even though they are probably not useful. Part of https://github.com/odoo/odoo/pull/52081 closes odoo/odoo#52114 X-original-commit: 7760898de4e14fa30db1db87dfa05276bfcaa2bb Signed-off-by: Quentin Smetz (qsm) <qsm@odoo.com>
2020-02-05[IMP] website, *: make theme custo options act as simple snippet optionsqsm-odoo
* web_editor, theme_bootswatch Instead of having an entirely dedicated system for theme options in a third tab of the left panel, those theme options are now simple snippet options. See the customizeWebsite generic method. This allows to make any option available in the third tab or on any meaningful element like the header or the footer. This also allows to take advantage of all the features of the left panel: dependencies, visibility update, etc. Note: same as before, those changes do apply the color/size/layout immediately on the website, even if not saved. Changing that behavior is complex and might be the job of another task. Part of https://github.com/odoo/odoo/pull/41166 task-2088298
2020-02-05[REF] website, web_editor: move theme customization to edit modeSamuel Degueldre
Previously, theme customization was done through a modal dialog in the website module, this was not very user friendly since the rest of the customization for the website design was done from edit mode, meaning the user had to exit edit mode to customize things such as theme colors or fonts. It was also rather confusing to have these seemingly related things in completely unrelated places. This commit moves all of the options that used to be in the theme customization modal into a new tab in the editor's left panel. This commit is mainly just about rendering the old modal as a third left panel content. See next commit for deeper changes. Note: same as before, those changes do apply the color/size/layout immediately on the website, even if not saved. Changing that behavior is complex and might be the job of another task. Part of https://github.com/odoo/odoo/pull/41166 task-2088298