Hitting enter after a heading should create a paragraph

[GoogleCodeExporter]

What steps will reproduce the problem:
1. Create a Heading (like a H1)
2. Hit enter
3. Start typing... apparently you are typing into a new paragraph.
4. Hit enter
5. Depending on the browser, it will either create a <br/> instead a new 
paragraph (like with Chrome), or do nothing (like with FireFox 4).

What drives me nuts is that 99% of the Rich Editors does this BR-thing too. So 
hitting enter normally creates new P, but sometimes a new BR instead, which is 
confusing for the user. Also I don't want users to create BR-s (because they 
love to do that, ruining typography) unless they are knowledgeable and hit 
shift+enter. Apparently, the issue is that hitting enter in a heading will not 
create a "p" element, so you start adding characters directly after the H1 
end-tag. Do browsers make it impossible to fix?

Version 61 I believe (the current online demo on your site), Windows 7, FF4, 
Chrome 10.0.

Original issue reported on code.google.com by daniel.d...@gmail.com on 8 Apr 2011 at 12:46

[GoogleCodeExporter]

Yeah, I forgot to mention that I know of an editor that does not have this 
issue, Loki: https://apps.carleton.edu/opensource/loki/demo/
So somehow it can be solved after all.

Original comment by daniel.d...@gmail.com on 8 Apr 2011 at 12:54

[GoogleCodeExporter]

Thanks for your report. We will treat this as an enhancement request and 
schedul it in a future version of Whizzywig.
~Jorogo

Original comment by unve...@gmail.com on 23 Jun 2011 at 10:17

• Changed state: Accepted
• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

Using Whizzywig 63
==================
Press enter at end of <H1>
 *Chrome 12* creates a <div>
 *Opera 11.5* creates a <p>
 *Internet Explorer 9* creates a <p> 
 *Firefox 5* creates a text node, followed by <br/><br/>
 *Safari 4.1* creates a <div>

Opera and IE9 get it right.

Original comment by unve...@gmail.com on 21 Jul 2011 at 1:21

[GoogleCodeExporter]

Despite what I said earlier regarding other editors, enter seems to work 
correctly in TinyMCE and CKEditor too. (However, in those spell checking is 
disabled (and it goes out if sync if you force it), which for me rules them 
out. I hope there's no connection between that and the correct enter 
behavior...)

Original comment by daniel.d...@gmail.com on 26 Aug 2011 at 7:36

[GoogleCodeExporter]

Will be addressed in the next release. i.e.
Press enter at end of <H1>
 *Chrome* creates a <P>
 *Opera* creates a <P>
 *Internet Explorer* creates a <P> 
 *Firefox* creates a <P>
 *Safari* creates a <P>

Browser spell-checking will not be inhibited.

Original comment by unve...@gmail.com on 10 Nov 2011 at 3:45

• Changed state: Started