Romain Derie
7859df06cd
Since [1] the website builder is able to warn and prevent a user that a snippet is not going to be able to be saved in a field if that field is going to be sanitized. Back then, we didn't mark the steps snippets as such as we were planning to make it work in sanitized field by refactoring the JS code, as we did for the s_map snippet at [2]. It was supposed to be done at [3] but was cancelled as it was making the UX worst due to some flickering + we are also working on [4] to make the sanitation conditional and able to be bypassed. Note that the conflict with the sanitation for the steps snippet starts in saas-15.2 with its connector improvement/ refactoring [5]. Those connectors are now svg elements targeted by the options, which ultimately crash if those connectors are not found, which is the case when the DOM is going through the sanitizer as it is removing SVGs. [1]: https://github.com/odoo/odoo/commit/8920f7d09fe020c8f182b3ea1acbafcb955afdce [2]: https://github.com/odoo/odoo/commit/c2e9bd0e60014b6a42931cf300e0f89f8cf7c225 [3]: https://github.com/odoo/odoo/pull/96734 [4]: https://github.com/odoo/odoo/pull/97398 [5]: https://github.com/odoo/odoo/commit/aba31e9f2d8a44ce1586403f2a621a6caeed57b4 X-original-commit: 515a7e1705bed48f10e844d0f183dddeda27277d Part-of: odoo/odoo#99014