The breaking text doesn't work into the text box both of frontend and of backend on FireFox 3.6.8. and Explorer 7 and 8.

For example if I write a long text like this:


Automatically the text should go to the second line into the box. But the text goes infinitely to under the text box.
It happens also in backend on FireFox and Explorer. No problem on Chrome and Safari.

Hi campi,

Thank you for you post.

I think you will find that your issue is CSS related rather that a bug in your code.

The editor works by writing the code while in WYSIWYG mode, once the code has been written CSS controls how the html is displayed. Browsers can differ on how they interperate CSS so it is common during development for something to look OK in one browsers and broken in another.

Without viewing your templates style-sheets it is impossabile to be sure but the CSS atreburite 'Word-Wrap' maybe the answer you need.

.break-word {
word-wrap: break-word;
}
I have found a topic on your issue which i hope will be of asistance to you, please see: www.webdesignerwall.com/tutorials/word-wrap-force-text-to-wrap/

Take care,

P

Thank you. I needed exactly this.
I put ".break-word {word-wrap: break-word;}" into my template's Css.But I have one question:

To apply to all CK Editor(targets), which files do I have to put the following lines in?:

<p class="break-word"> long text</p>

Thank you

It isn't working;(

I put the line {word-wrap: break-word;} into my template called theme.css.
And then I set up to use "custom template.css" inserting the pass to this css file from CK Editor plugin.
I seem I correctly set up but it doesn't work.

What is wrong?

Hi campi,

Sorry to hear that.

As I mentioned before “it is impossible to be sure” there are many factors involved – it could be your html code but it is impossible to know without actually seeing what you are trying to do. Either way - some browsers have determined that your code should not break while other seam for more forgiving.

Maybe if you added a fixed width to your class and used overflow:auto; it might be another way of getting around your issue.

However, it doesn’t sound like an issue with the editor and our support is really tailored to that.

Thanks


P