id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
8868	Hitting return should create a new default block element.	Brian		"Sorry if the title isn't very descriptive, but here is the issue. If I add a <div> tag to the document, then hit enter/return, it creates a new <div> tag even though the default block element is a <p> tag. This is a major problem for clients when they copy/paste content that may have a stray <div> tag. If they paste something with a <div> tag, then start typing new text after that, the <div> tag hijacks the current block level element being used and there is no way to return to it without editing the source.

Personally I have an issue with this because it does not allow me to insert a custom <div> tag around, lets say, an image. I'd like to create something such as:

Expected:
<p>text</p>
<div class=""figure""><img src=... /></div>
<p>text</p>

Actual
<p>text</p>
<div class=""figure""><img src=... /></div>
<div class=""figure"">text</div>

Lastly, you may wonder why I'm adding a div with the class of ""figure"", well, because CKeditor does not recognize the <figure> element.

Expected behavior:

<p> tags should be the default block level element _always_. Regardless of what was preceding it. Hitting return/enter should use that default block element, not continue to use the previous block element. Ideally it would recognize <figure> as well. I'd  like to be able to insert a <figure> element containing an image, hit return, then start typing text into a <p> tag, not a <div> or <figure> tag containing text. HTML5 support was added to a recent version, but apparently someone forgot about the <figure> tag."	Bug	confirmed	Normal		General	3.0