Data and features activation based on configurations
|Reported by:||fredck||Owned by:||Reinmar|
|Priority:||Normal||Milestone:||CKEditor 4.1 RC|
Description (last modified by Reinmar)
The basic idea is introducing filtering that acts on the HTML accepte by the editor and the feature available in it.
An as easy as possible way to configure the elements, attributes and transformations (e.g. <b> to <strong>) that the editor should support.Note: transformations part was extracted to #9989. By default, this configuration is defined by the plugins available in the editor. E.g. remove the link plugin and <a> will not any more be accepted. Developers can define this configuration. At that point, plugins, or part of their features, get enabled/disabled based on the configuration.Note: dialogs integration with allowed content filter was extracted to #9990. All data input (especially paste) in the editor will be then filtered, based on the configuration. Transformations first and then elements/styles checks. Input data normalization will take place before filtering, bringing to an acceptable DOM structure. Special pasting plugins, like Paste from Word, will be reviewed to use the normalization+filtering system.Extracted to #9991. Selection context participates on filtering as well. A <h1> editable should restrict the editor features accordingly. Another example, a selection inside <a> should not permit <a> elements being inserted.
As a result only allowed HTML will reach the contents and only allowed plugins (or their features) will be enabled.
List of subtickets
Change History (36)
comment:3 Changed 4 years ago by Reinmar
- Description modified (diff)
- Status changed from new to confirmed
comment:9 Changed 4 years ago by Reinmar
- Owner set to Reinmar
- Status changed from confirmed to assigned
comment:12 in reply to: ↑ 11 Changed 4 years ago by Reinmar
comment:25 follow-up: ↓ 28 Changed 4 years ago by Reinmar
comment:32 Changed 4 years ago by Reinmar
- Resolution set to fixed
- Status changed from review_passed to closed