Without further details it’s a bit hard to get what you mean. If you’re in “text mode” and not in “visual mode”, that’s the native behavior of the TinyMCE editor.
Does your problem occur only in widget or even in pages/post?
Interestingly I also have the same problem in bbpress using the tinymce editor there.
I’m sorry I did not explain this well:
Basically when we type we see the text as already double spaced, then when we submit/publish content it appears single spaced. This is confusing to users because they do not enter an extra return/enter to form paragraphs because the double spacing is showing already in the editor.
You didn’t specify if you are using text mode or visual mode.
Anyway, I think it would be nice if you could provide a screencast which explains the problem visually.
Visual mode. Anyway I do not think it’s this plugins fault, it’s likely a theme css issue I’m guessing.
View post on imgur.com
See the text is double spaced inside the editor, then outputs single spaced. Or in other words….. the line spacing is so large inside the editor in comparison to the actual output after submission, that users often do not add additional spaces to make paragraphs.
Note: I have this issue on every plugin, not just this one. It’s not an issue of shift enter, because even when doing shift/enter we still have to do a shift/enter twice to make a paragraph.
View post on imgur.com
Here is an example of using shift/enter then another enter to make a paragraph, but then the final out put shows no paragraph.
Sorry about the bad quality, I’m new at this…
Here is a better look:
View post on imgur.com
Your screenshots do not show any widget created with our plugin. They look like bbpress forms, which are totally unrelated to our plugin. As you said it’s likely not an issue depending on our plugin, but due to something else altering the behavior / styling.
I would suggest you to selectively disable plugins and temporarily switch to another theme, in order to find the cause. You may find additional suggestions in the troubleshooting section of our FAQ.
Once you find the culprit, you should ask in the relevant support forum.
Since this issue doesn’t seem related to our plugin, I am going to mark this topic as resolved.
