Keying a return creates a new div element in the editor

[cedarcreek]

So I have a snippet set up that's working fine. Today I added a new div element for a news section on a page. This element is within an existing snippet. When I put my cursor in this element and begin typing, all is fine. However, if I hit "return" on my keyboard while the cursor is in this div, the CMS creates a NEW div within the existing one, with a blinking cursor waiting for some text. Why? This makes no sense at all. If I do a shift-return, it drops one line like it should, and stays within the original div.

I've never seen this before, and I can't imagine why this would be a "feature". None of my other Snippetmaster sites do this, that I know of.

I just checked this out on the rest of the snippets on this site, and it does the same thing! Hitting enter within the CMS editor creates a NEW div of the existing element...instead of a new paragraph.

???

[cedarcreek]

I just discovered that the placement of the snippet tag has something to do with this. It's certainly a bug.

If you place the snippet outside the div (in my case, my main content div), the results are unpredictable. Sometimes you'll get a <p>&nbsp;</p> on return, and other times you'll get a new div, inside the current div, with the same style attribute.

If you place the snippet inside the div, hitting return does the expected <p>&nbsp;</p>.

So, case closed for now, but this should really be fixed. There is absolutely no reason to create a new element (other than a paragraph or list item) when hitting enter in the CMS editor.