id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
5694	When config.enterMode = CKEDITOR.ENTER_BR & config.forceEnterMode = false, pressing enter inside a <p> (or <div>) should insert a new <p>	Jonathon Sim		"This is by analogy with the behaviour when enterMode = ENTER_P, when your text is formatted with <p> then pressing enter inserts a new <p>.  Within text formatted with <div>, enter inserts a new <div>. In essence ""enter"" honours the format of the text you are editing

With config.enterMode = ENTER_BR however, enter always inserts a ""<br>"". 

With the attached patch ""enter"" inserts a new paragraph block if you are currently in a paragraph, a div within <div>s, and <br> otherwise.  forceEnterMode=true overrides this and always uses br.

In practical  terms, this is desirable because it provides users a way to enter text with paragraphs, which is otherwise impossible (for instance by chosing Format: Normal from the format dropdown), and also matches the behaviour fckeditor used.  And most users with enterMode = ENTER_BR  do so not because we are fundamentally opposed to semantically correct markup, we just have users that don't expect the ""blank line"" worth of space at the top of the text that it entails.
"	New Feature	closed	Normal		UI : Enter Key		wontfix