Opened 10 years ago

Last modified 10 years ago

#12343 confirmed Bug

ACF does not play well with basicstyles

Reported by: Wiktor Walc Owned by:
Priority: Normal Milestone:
Component: Core : Styles Version: 4.1
Keywords: Cc:


  1. Start CKEditor with:
CKEDITOR.replace( 'editor1', {
    allowedContent : 'u i b'
} );
  1. Enter "foo bar", select it and press "B", "I" buttons.
  2. Result in CKEditor:
    <em><strong>foo bar</strong></em>
    (it can be easily noticed in the elements path).

Although getData() returns properly <i><b>foo bar</b></i>, such behavior is buggy. When CSS styles are defined for <b>/<i> they will not be applied for <strong>/<em>. Besides it is misleading for anyone configuring ACF.

Change History (2)

comment:1 Changed 10 years ago by Piotrek Koszuliński

This is a lack of full integration between basic styles and ACF. Filter will transform strong into b when loading data, but ACF is ignored inside editor, when a style is applied. This is much higher level of integration - possible, but we haven't got time to achieve it. Note that this issue is not related to basic styles only, but it's very general - e.g. image will still use inline styles even though ACF is configured to accept attributes only.

PS. I think that there may be a ticket for this already, because it's obviously a known issue.

comment:2 Changed 10 years ago by Jakub Ś

Status: newconfirmed

I have not find any such issue so I'm confirming this one.

Note: See TracTickets for help on using tickets.
© 2003 – 2022, CKSource sp. z o.o. sp.k. All rights reserved. | Terms of use | Privacy policy