Hello community.
We have had a problem with the WYSIWYG editor (CKEditor) for a really long time. For more than two years. We have never been able to find an easy way to reproduce the problems though but now we have one that we can reproduce all the time. We added the fullscreen option/feature to the CKEditor config because it makes it a lot easier to use with large contents.
However it seems that the WYSIWYG editor is not fully compatible with how the ZK framework is used with the Backoffice widgets. When a Backoffice widget opens up and dims the background like for example the create wizard and you click on the fullscreen option which adds another layer of dimd popups the WYSIWYG editor it creates a really bad problem. The javascript from CKEditor will add a dimming layer on top of itself colliding with the one the Hybris Backoffice widget already placed blocking itself.
We have gotten similar problems with other CKEditor features such a table properties, links and media which open up windows and when you already are in a create wizard and do this the windows CKEditor opens end up behind the Hybris Backoffice modals/wizards. However we have only been able to find a 100% reproducible situation with the fullscreen option that we can recreate every time.
Note that if we use the WYSIWYG editor straight on an editor area that is not in a Hybris Backoffice modal/popup/details view but in the collection browser we never have these problems. Then it always works and all features work but as soon as we are in a Hyrbis Backoffice modal things start to collide. So we suspect the problem is that Hybris Backoffice opens up modals which dims the background and then when you use the WYSIWYG editor in these modals it will for some features open up another one in front which then clashes with the already dimmed background. We have spent quite a lot of time trying to resolve this ourselves but the only solution we have found is that we never use WYSIWYG editors in create wizards and details views. Are you able to reproduce this and perhaps fix this?
After pressing the fullscreen feature from the create wizard: 