Uploaded image for project: 'In-Portal CMS'
  1. In-Portal CMS
  2. INP-94

FCKEditor behavior, when ENTER is pressed

    XMLWordPrintable

    Details

    • Type: Feature Request
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 4.3.9
    • Fix Version/s: 5.0.0
    • Component/s: Admin Interfaces
    • Labels:
      None
    • Additional information:
      Hide

      Mentioned above code should be added to "inp_fckconfig.js" file.

      FCKConfig.EnterMode = 'br' ; // p | div | br
      FCKConfig.ShiftEnterMode = 'p' ; // p | div | br

      When such settings are already present in your version of this file, then they should be replaced with given ones.

      Show
      Mentioned above code should be added to "inp_fckconfig.js" file. FCKConfig.EnterMode = 'br' ; // p | div | br FCKConfig.ShiftEnterMode = 'p' ; // p | div | br When such settings are already present in your version of this file, then they should be replaced with given ones.
    • External issue ID:
      113
    • Copy Issue Key:
    • Patch Instructions:

      Patches must be submitted through Phabricator.

      Description

      Currently FCKEditor adds paragraph tags (p) around any text when text is entered OR ENTER is pressed in editor area. Alternatively when Shift+ENTER is pressed, then line break tag (br) is added. This is not very comforting especially, when additional margin is added to paragraph tags (p) by site css.

      I propose to invert FCKEditor default behavior like this:
      1. when ENTER is pressed, then normal line break (br) appears;
      2. when Shift+ENTER is pressed, then and only then paragraph tag (p) should be inserted.

        Attachments

          Activity

            People

            • Assignee:
              alex Alex
              Reporter:
              alex Alex
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: