The '<'span'>' and '<'span class'>' entries in footnotes.ckeditor5.yml are incorrect. The plugin uses '<'span'>' only in the editing downcast (widget UI), not in the data downcast (saved HTML). Declaring span elements in the elements list makes the footnotes plugin claim schema ownership of all classed spans, which conflicts with any other plugin or GHS rule that also uses '<'span class'>' (e.g. text styles, inline formatting).
When in ckeditor, try adding in a class that is not related to this module to the span element. It will not take due to this bug.
Removing '<'span'>' and '<'span class'>' resolves the conflict without breaking any functionality, since editing-view elements do not need to be declared.
| Comment | File | Size | Author |
|---|
Comments
Comment #2
gmatteo commentedComment #3
scott_euser commentedThanks for raising and for the contribution. Can you please create as a merge request so tests run, add test coverage as appropriate, and provide a link to an example conflicting module along with clear steps to reproduce from a clean drupal 11 install (eg standard profile). Thanks!
Comment #4
scott_euser commentedWith steps to reproduce eg with conflicting module could consider changing severity again...