#2 Bug 808418 fix, minimal tab support

closed
nobody
None
5
2004-01-30
2004-01-02
Phil Hassey
No

A modification to fck-1.3.1/js/fck_editor.js .

Based on the \n = br feature of 1.3.1, adds br on a \n,
but then turns two br's into a p.

Also added \t = 8 spaces

Discussion

  • Phil Hassey

    Phil Hassey - 2004-01-02

    diff -u style patch for 1.3.1/js/fck_editor.js

     
  • Frederico Caldeira Knabben

    Logged In: YES
    user_id=572424

    This feature is available from version 1.4.

    Best regards,
    FredCK

     
  • Frederico Caldeira Knabben

    • status: open --> closed
     
  • Phil Hassey

    Phil Hassey - 2004-01-30

    Logged In: YES
    user_id=575107

    (all of these comments are applicable to:
    config.UseBROnCarriageReturn = true;)

    I tried 1.4, and I'm glad to see tabs were added into it.
    However the BR / P issue was not changed. If you hit enter
    a few times, it never turns those BRs into Ps.

    Thus, if I highlight any text and click "Align Right" or "Align
    Center" all the content will be re-aligned.

    Thanks,
    Phil

     
  • Frederico Caldeira Knabben

    Logged In: YES
    user_id=572424

    You must decide to use BRs or Ps... you have to think about
    the convenience of that. For example, I never use the ENTER
    as BR feature only because there are so many HTML limits on
    that that I prefer to find other solutions (like the
    SHIFT+ENTER or the CSS solution). One of these limits is the
    alignment. On HTML the alignment is done by the P tag so if
    there is no Ps available, everything is aligned togheter.

    Best regards,
    FredCK

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks