Hi,
What's the situation with the <br />s and <p>s now that 2.4 is out? I'm so glad that firefox can now generate <p> tags just like ie. Only thing is I read that it was going to be implemented so that if the user pressed enter once it would put in <br />, twice and it would put in <p>. This is perfect IMO, much better than having to tell users to press shift-enter. In fact, isn't this how MS word does it? it would be good to emulate this behaviour as so many users know it already.
I thought maybe the UseBROnCarriageReturn property would affect this but it doesn't seem to make any difference. Is there any other options or am I stuck with <p> </p> all over the place and unpredictable line spacing?
Many thanks,
Greg Smith
What's the situation with the <br />s and <p>s now that 2.4 is out? I'm so glad that firefox can now generate <p> tags just like ie. Only thing is I read that it was going to be implemented so that if the user pressed enter once it would put in <br />, twice and it would put in <p>. This is perfect IMO, much better than having to tell users to press shift-enter. In fact, isn't this how MS word does it? it would be good to emulate this behaviour as so many users know it already.
I thought maybe the UseBROnCarriageReturn property would affect this but it doesn't seem to make any difference. Is there any other options or am I stuck with <p> </p> all over the place and unpredictable line spacing?
Many thanks,
Greg Smith
RE: <br /> and <p> now that 2.4 is out
According to the release notes UseBROnCarriageReturn is no longer valid.
... The EnterMode setting can now be used to precisely set the enter key behavior. (it doesn't explain how)
RE: <br /> and <p> now that 2.4 is out
I'll have a play with the new EnterMode setting.
RE: <br /> and <p> now that 2.4 is out
OK, from looking at the source of the test form at http://www.fckeditor.net/nightly/fckedi ... ple12.html I think there's two new properties.
It seems that there's 'EnterMode' and 'ShiftEnterMode' and they can be set to 'p', 'div' or 'br'.
This sort of sorts the issue for me but I THINK if 'EnterMode' is set to 'br' it stops it from creating the initial paragraph tags (just firefox?) which will then lead to invalid xhtml (text outside of <p> tags).
I suppose the holy grail for me would be:
1. If enter is pressed once a <br /> is created, twice and the <p> tag is closed and opened to start a new paragraph.
2. The text is always in at least 1 <p> tag if set to xhtml strict so that the page will still validate.
I don't think I'm the only one.