shiftEnterMode set to CKEDITOR.ENTER_P doesn't report P tag to ACF

[dilip]

EDITED

1. Configure editor in the following way:

   var editor = CKEDITOR.replace( 'editor1', {	
   				    toolbar:[
   						{ name: 'document', items : [ 'Source' ] }, { name: 'basicstyles', items: [ 'Bold', 'Italic' ] }, { name: 'styles', items: [ 'Format' ] }
   
   					],
   					enterMode : CKEDITOR.ENTER_BR,
   					shiftEnterMode : CKEDITOR.ENTER_P
   

2. Go to page with editor, switch to Source and PASTE this<p>issue</p>
3. Switch to WYSIWYG and to Source one more time
4. Result is this<br />issue. The same thing happens for this code:

   <p>issue</p>
   this
   <p>issue</p>
   <p>issue</p>
   

It seems to me that ShiftEnterMode doesn't report P tag to ACF. To confirm this I have added { name: 'styles', items: [ 'Format' ] } to toolbar and this time it has worked without problems.

NOTES:

1. Problem can be reproduced from CKEditor 4.1
2. It doesn't occur if you turn off ACF - allowedContent : true or add plugin which reports P tag to ACF
3. There is different issue (I'm not 100% sure if this is a bug) when you write in editor. Please see #10543.

[Jakub Ś]

Could you describe more precisely what do you mean because I don't understand your request.

Editor doesn't remove P tags when BR mode is used. Please explain in plain step by step scenario what is happening.

[dilip]

Replying to j.swiderski:

Step 1) set web config like this

config.enterMode = CKEDITOR.ENTER_BR; config.shiftEnterMode = CKEDITOR.ENTER_P;

Step 2) in source write "this<p>issue</p>"

Step 3) click again in source (design mode) Step 4) now click again in source (source mode)

check source it remove the p tag and you will find text "this</br>issue"

[Jakub Ś]

I have tried CKEditor 4.1.2 in every browser and didn't get this issue.

1. Please describe in which Operating System and Browser you get this.
2. Are you using one of three packages: standard, full, basic or you have created your editor with builder and there are some third-party plugins included?
3. Could you send us your build-config.js?

[dilip]

Replying to j.swiderski:

It is straight forward issue in all browser. I am using full version of 4.1.2.

please find the attached config for your reference.

[Jakub Ś]

Well in my case issue isn't straight forward.

I have cleared cache in every browser then I have tried your simple TC but no luck. Code test<p>test</p> wasn't changed.

1. I was talking about build-config.js file and not config.js so if possible please attach this one.
2. Could you perhaps download full package and try once more? This time please just download editor, drop it on server and try running it on browser (you can clear cache as well). Please try running editor only without your application or custom scripts that might influence this problem.

[dilip]

Replying to j.swiderski: Please find the attached build.config.js

issue is not coming if you only set config.enterMode = CKEDITOR.ENTER_BR;

issue comes when you have both mode on config.enterMode = CKEDITOR.ENTER_BR; config.shiftEnterMode = CKEDITOR.ENTER_P;

[Jakub Ś]

issue comes when you have both mode on config.enterMode = CKEDITOR.ENTER_BR; config.shiftEnterMode = CKEDITOR.ENTER_P;

I did that.

Could you perhaps check what i have written in last comment:

Could you perhaps download full package and try once more? This time please just download editor, drop it on server and try running it on browser (you can clear cache as well). Please try running editor only without your application or custom scripts that might influence this problem.

[dilip]

Replying to j.swiderski:

I got the exact case.

If you are use default toolbar then its working fine but if you customize anything then it will not work. just use below code it start giving issues.

<script type="text/javascript"> CKEDITOR.replace( 'txttest', {

toolbar:

[

{ name: 'document', items : [ 'Source' ] }, { name: 'basicstyles', items: [ 'Bold', 'Italic' ] }

]

}); </script>

can you please check and give me any workaround.

Thanks for your help.

[Jakub Ś]

@dilip I have managed to reproduce this problem. If possible, please provide all necessary details when reporting bugs.

I have modified your Description. You will find two workarounds there.

[Piotrek Koszuliński]

Yes, you're right that shiftEnterMode does not register its required content.

[Piotrek Koszuliński]

Pushed ​t/10537 on dev and tests.

[Piotrek Koszuliński]

Fixed with ​git:c72892f on dev and 07597aef on tests.