On CKE4, to avoid the stripping of HTML elements and attributes, this module states that "If you use the Limit allowed HTML tags and correct faulty HTML filter, do not forget to add
On CKE5 this is no longer possible, as the Linit allowed HTML Tags textarea field is readonly and just reflects what has already been whitelisted at the pluign definition level.
Right now, this module is setting elements: false.
This means bootstrap tabs are not working out of the box with Limit HTML Allowed tags, as certain HTML elements and attributes are stripped.
It is responsibility of this module to indicate which elements to keep in order to work with the Limit allowed HTML filter.
- Add Bootstrap tabs to a filter
- Mark the "Limit allowed HTML tags" setting
- Create a tab. It renders OK inside the CKE5
- See the entity. The tab is broken as several classes and even HTML elements will be missing (they will depend on the CKE5 configuration and which other plugins whitelist which elements/attributes)
Add the rules to the elements: entry of the ckeditor5 plugin definition.
None
None
None
Active
2.0
Code
Moving to needs review.
I've created a MR. Instead of whitelisting all attributes as it was proposed for CKE4, I've added stricter rules that (when possible) will whitelist only the specific classes and data-attributes used on this plugin.