Data and features activation based on configurations

[Frederico Caldeira Knabben]

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.

• 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.

• 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.

As a result only allowed HTML will reach the contents and only allowed plugins (or their features) will be enabled.