search

tiff / wysihtml5

Open source rich text editor based on HTML5 and the progressive-enhancement approach. Uses a sophisticated security concept and aims to generate fully valid HTML5 markup by preventing unmaintainable tag soups and inline styles.
http://xing.github.com/wysihtml5/
MIT License
6.48k stars 995 forks source link

Editor becomes unresponsive after toggling containing div #505

Open cmatskas opened 10 years ago

cmatskas commented 10 years ago

Hi, we use the rich text editor in a wizard where each step is a div whose visibility is toggled depending on the wizard progress. When first toggling the div that contains the editor, we can see and interact with the textbox just fine. However, if the user chooses to go back or forward and then decide to return to the step/div that contains the editor, then the following happens: The content disappears from from editor text box The editor cannot be clicked/edited and it's frozen

At first, I thought that this was due to the fact that we were initializing the editor every time the user accessed the step/div in question, so we now only instantiate the editor once at document.ready(). However this has not fixed the problem.

My suspicion is that the problem is related to the iframe but I'm not sure what to test for. Could you please help with this as it is stopping us from releasing our website? Thanks

Waxolunist commented 10 years ago

You will not get any further for a long time. This repo is not maintained anymore. I would recheck the dependencies of your website. As alternative I'd suggest a still maintained fork of this editor. eg http://edicy.github.io/wysihtml5/

cmatskas commented 10 years ago

Hi @Waxolunist, thanks soooo much for the quick response! How different is the forked version? I'm happy to use it as long as there no major differences. What do you mean by "check the dependencies"? The only thing we do as the user progresses through the wizard is to show and hide divs in the page for each step. The first time we load the step/div with the editor, all is fine. But if the user goes back or forward and then returns to the step with the editor, even though the editor is there, the content is missing and the editor is unresponsive.

Any pointers? Thanks again for your time and effort

Waxolunist commented 10 years ago

The fork should be api compatible. There are no major differences, except more features. I had in my bootstrap wrapper no major problems when switching.

I mean with "check your dependencies", that you want to go live with a website which depends on widgets, which haven't been updated for more than two years.

For your specific problem I don't have any pointers, because I have no experience with your usecase. I'd suggest to reinitialize the editor every time you come back to the page.

cmatskas commented 10 years ago

@Waxolunist again, thanks for your response. You are right about the dependencies, but I thought that the plugin was actively maintained. I will switch to the forked one but since we only do basic stuff I suspect it will all be fine. I've tried re-initializing every time the div becomes visible but it doesn't seem to work... back to the drawing board :(