Empty Paragraph Tags at beginning of Page/Table

Looking for a solution to this problem as well. Just a note I've observed it seems to be more prevalent in IE7 although it will happen in IE8 and Firefox under certain (seemingly random) conditions.

I'm hoping for a solution to this as well - Its 100% repeatable on Firefox 3.6.12 on Ubuntu, and is quite problematic for our users. As a workaround, I've set enterMode to CKEDITOR.ENTER_BR which actually stops the extra blank paras, but we'd like to avoid this if possible.

I am also looking for resolution to this issue.

I've noticed it only occurs when startupFocus is enabled. Issue occurs in latest version (3.5.2) in IE8, IE9, and Chrome.

Firefox 3.6.15 appears to correctly place initial focus in the first cell of the table.

We are having the same issues, does anyone have a solution for this? It's not acceptable behavior for our clients to have this code inserted by default <p>&nbsp;</p>. Where is the setting to turn off "autoparagraph"?

See http://docs.cksource.com/ckeditor_api/s ... oParagraph

Changing config.autoParagraph = false did not solve this problem for me in Chrome (didn't test other browers). I have a table being placed via a template, and my code looks like this once I switch to Source

My template code is:

      {
        title: 'Single Column Table',
        image: 'oneColumnTable.gif',
        description: 'Creates a standard single content table.',
        html: '<table class="cTable one-column"><tr><td class="theader">Title</td></tr><tr><td>Content</td></tr></table>'
      },

And the output code looks like this:

<p>
</p>
<table class="cTable one-column">
   <tbody>
      <tr>
         <td class="theader">
            Title</td>
      </tr>
      <tr>
         <td>
            Content</td>
      </tr>
   </tbody>
</table>
<p>
</p>

These extra paragraph tags are driving me crazy because they are a real problem for my users to control, especially since they only appear until the code is refreshed via either Source-toggling or page save.

Also, removing these <P> tags from within the visual editor DOES NOT remove them. When toggling the Source, they come right back. It's horribly frustrating, because this has been an issue since the inception of this editor and have never been properly address.

I currently have these variables set via my config file:

config.autoParagraph = false;
config.fillEmptyBlocks = false;
config.shiftEnterMode = CKEDITOR.ENTER_P;
config.enterMode = CKEDITOR.ENTER_BR;

Nothing here makes a difference. Still having <P> tags placed above and below template. I even attempted to wrap the entire table in a <div> tag, and <P> tags were STILL placed above and below. What am I missing here?!?!

I am also having the exact same problem as ekazda. If anyone has any suggestions or hints, they would be very greatly appreciated.

This issue, bug or now I would already call it a feature, still persist after many, many years. I have a very simple HTML structure where I have floating elements. CKEditor with this feature thinks it is a great idea to add empty <p> </p> tags at the end of each closing element (fieldset) thus rendering my efforts to neatly float these items void.

I'm using Drupal 7.34 and I've added CKEditor 4.x to it. Every time I open to edit my page, I do not see these tags. Every time I submit my edit, these tags appear. Very simply:

<div class="grid group">
    <fieldset class="col span_1_of_3">
        <p>
            Content
        </p>
    </fieldset>
    <fieldset class="col span_2_of_3">
        <p>
            Content
        </p>
    </fieldset>
</div>

 

After I submit the content and inspect the page structure:

<div class="grid group">
	<fieldset class="col span_1_of_3">
		<p>
		Content
		</p>
		<p>	</p>
	</fieldset>
	<p>	</p>
	<fieldset class="col span_2_of_3">
		<p>
			Content
		</p>
		<p>	</p>
	</fieldset>
	<p>	</p>
</div>

This is not the CMS' fault. I've also seen this happen with Wordpress. It's CKEditor. I've tried adding the autoParagraph false with no effect. I will not accept changing <p> tags to <br> as a solution as it is a modern approach to good sites using CSS on p-element, not adding <br> as a paragraph break. You seriously cannot fix this?