Awkward text editing

1. If I select a font size and start typing, it does not take effect. I need to reslect the text and then change it to a different size, then select the size I want for it to take effect.

2. If I type a line and follow it by several carriage returns, the line does not advance by more than one line. If I then start typing the text begins at the end of the previous line. The only time the carriage returns work is if I insert them between existing text.

I do have the config.js set to the following;
config.enterMode = CKEDITOR.ENTER_BR;

Is there a work around for these issues?

1) That is by design. The font size cannot be applied to a blank selection. the font size is applied by adding a span tag around the selected text, if no tet is selected, the span tag cannot be inserted.

2) I am not able to reproduce this.

I have an html editor instance set to use the BR Enter mode as well, if I hit the return key, a BR tag is applied at the end of the string for each return I hot.

Click on the Source button to see how the br tags are being applied. It could be a conflicting style causing the other br tags to be ignored.

I tried the CR problem again in 2, and also could not reproduce it. It may be due to a sequence of events.

Is your answer to 1, a limitation of HTML? No other text editor works like this that I have ever used. People used to entering text in Outlook or Word for example will setup the font and size, and then start typing. It is frustrating to have to redo a selection after the fact.

I was able to recreate the carriage return problem in 2 mentioned above.

If I type something, then hit carriage return a few times, and then press the shift key; the cursor jumps back to the end of the line I typed before hitting those carriage returns.

If I don't hit the shift key the text stays on the correct line.

Hi George,

You can set the font-size and color so that it appears the way you want it to in the HTMLEditor instance window by altering the css (see below) - but this just makes it 'appear' right in that window.

The idea of there being no initial style applied is to ensure that whatever is entered in your editor area (unless you specify a new font-size from the drop-down) will take on the style that you have specified in your stylesheet or in-line css of the containing body, div or span on the page/template that the HTMLEditor entry is output to.

Check the page or template that the Editor code is output to, and set the style for the containing element (body, div, span or email template line) and apply the required style to that element.

If you just want to change the appearance of the (apparent) default style for the Editor input instance, open the Editor stylesheet (webassist/ckeditor/contents.css) and apply those same styles to the body rule - at about line 6)*. That will not change the format of the output, but you will have taken care of that by setting the style of the element that it is output to.

You could also attach your site stylesheet to your HTMLEditor as per my reply to your other post.

* (You may need to clear your browser cache to see the change.)

Could you create and upload a new instance of HTMLEditor on a blank page, and provide a link to it so that we can see what is happening with the return/shift problem?

I have simulated (what I believe may be) your set up, 18px font size, breaks instead of paragraphs, here. How does your pressing 'enter' compare to this?

I discovered that the carriage return problem with the HTML editor may be unique to the Google Chrome browser.

If you go to

contactus.php

with Google Chrome, you can see the problem of carriage returns demonstrated.

type in some text and hit several carriage returns.
Then press the shift key and type a letter.

you will see the cursor go back to the end of the first line you typed. Sometimes you don’t need to type anything before the cursor jumps back.

One note; I do have spell check as you type enabled.

Here is the test page example you requested,

George

The problem is definitely related to enabling ‘check spelling as you type’, and only in the Chrome browser.

If I uncheck the option in the editor, the CR problem goes away. I hope this can be fixed, because the automatic spelling check is a great feature.

Hi Neilo,

As to your other suggestion regarding the default font size; changing the content.css file worked great! I set it as follows;

font-family: Times New Roman, Times, serif;
font-size: 12pt;

At first I only changed the font size, and the email was correct, but the editor display showed a different font. Then I changed the Font-family in content.css and both were in agreement.

The email template already called out the size I wanted but until I changed the content.css, the size in the email was wrong.

Thank you,

George