Remove all font tags and style attributes from word processor content

Jason Aller's Avatar

Jason Aller

21 Nov, 2012 06:22 PM

Under "Preferences" => "Content" the setting for "Remove all font tags and style attributes from word processor content" is still combined instead of being split into separate checkboxes. Checking this single box will strip out font assignment, but prevents the underline and strikethrough features of the WYSIWYG editor from working.

  1. 1 Posted by Jason Aller on 21 Nov, 2012 06:31 PM

    Jason Aller's Avatar

    Editing text, underlining some with this option on and submitting leaves the text wrapped in empty <span> tags.

  2. 2 Posted by Bradley Wagner on 26 Nov, 2012 06:43 PM

    Bradley Wagner's Avatar

    Thanks for the feedback Jason.

    At this point, that is the expected behavior. I was just thinking that maybe we should change the WYSIWYG to use <u> and <s> in the event that you have the "remove style attributes" box checked.

    In your case, are you saying that you would keep the "remove font tags" checked and the "remove styles" unchecked if given the choice?

  3. 3 Posted by Jason Aller on 26 Nov, 2012 06:58 PM

    Jason Aller's Avatar

    The change you suggest would be a good one. I was approaching this beta to test out several things that I'm looking at for our redesign and knew I was testing for some of the editor improvements that haven't yet been implemented. I'm open to however this gets resolved, but in the long term I'm hoping that it will result in:

    1. editor is easy to use.

    2. admins get to protect users from themselves by removing buttons and functions where needed (site / content-type? / group or roll? / data def)

    This should allow easy removal of button, but parallel removal of that feature in the output, so if I remove the underline button the output shouldn't allow <u> or any <tag style="text-decoration: underline;"/>

    The ideal would be an editor approved features matrix where you list out all of the tags (or allow pasting in of a DTD) that will be allowed and/or exposed in the editor. There are some cases where I'd like to have support for <div> in the WYSIWYG, or be assured that the content will be wrapped in <p> tags.

    Typographically I want to be able to put in underlines where needed (ex: legal citations in their most complete form need them), but restrict underlines throughout most of the rest of the site because seeing underlines on the web causes people to think the text is a link.

    On the other hand I want to eliminate any <font> or style="font*" stuff entirely.

    I want to be able to expose different CSS classes for some instances of the WYSIWYG editor, perhaps attached to Data Definitions. Those that show up in the second drop down from the right on the top toolbar.

  4. Ryan Griffith closed this discussion on 31 Dec, 2013 01:34 PM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts


? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac