Changes between Initial Version and Version 1 of Ticket #5678, comment 3


Ignore:
Timestamp:
Jul 5, 2012, 2:00:11 PM (12 years ago)
Author:
Jakub Ś
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #5678, comment 3

    initial v1  
    1 **By default with every ENTER pressed the new paragraph is pasted**. "Blue Title" is h3 block element which wraps around line of text. It can’t be continued with every ENTER pressed because it would be impossible to get out of it.[[BR]]
    2 **By default there is also another option SHIFT+ENTER which inserts BR tags and allows to continue block (Blue Title) style **.[[BR]]
    3 So If the user wants to get out of “Blue Title” he/she presses ENTER , if he/she wants to continue the style he/she presses SHIFT+ENTER.[[BR]]
     1Block styles are not continued in new line while inline styles are continued with every line entered.  This is how CKEditor works.
    42
     3Style continuation is in one special case browser dependent issue. Some browsers such as Firefox, make it easy to move in and out element boundaries, while others IE, Opera and Webkit, don't. If you are using Firefox and you are out of element boundaries then the inline style won’t be continued. [[BR]]
     4Like I’ve said this very special case is browser dependent and is not CKEditor bug and was already described in #7796 and in #8195.
    55
    6 “Variable” style is an inline style which inserts inline tags VAR which are wrapped in P tags.
    7 Such inline styles are continued with every line entered.  Just look at font-styles. With every ENTER pressed a new paragraph with span is inserted.[[BR]]
    8 If you want to disable this style just unselect it from drop-down list.
    9 
    10 
    11 Style continuation is a browser dependent issue. Some browsers such as Firefox, make it easy to move in and out element boundaries, while others IE, Opera and Webkit, don't. If you are using Firefox and you are out of element boundaries then the inline style won’t be continued. [[BR]]
    12 Like I’ve said this very special case is browser dependent and is not CKEditor bug and was already described in #7796 and in #8195
    13 
© 2003 – 2022, CKSource sp. z o.o. sp.k. All rights reserved. | Terms of use | Privacy policy