Make "Escape HTML" filter skip the allowed tags of HTML filter

+1 for this change, but the version should be CVS.

You know, this is still a valid feature request, I believe..

This seems like a very logical feature to have. After all, if we have a white-list of tags not to strip, it's not that far of a stretch to imagine that we wouldn't want to escape them either =)

Considering @sun's change from Drupal 7.x to 8.x, does anyone have suggestions on a viable workaround to implement this while we wait for Drupal 8?

Thanks!
Henry

Nevermind. We were able to patch the filter module to add the option & functionality to "Escape disallowed tags" which basically combines the logic from the included "Strip disallowed tags" and "Escape all tags" options.

Was very quick and easy, took maybe 30 minutes to add this much needed functionality. Hopefully this feature request makes it into Drupal core someday. Works very well combined with CodeFilter module to allow much safer, yet permissive Forum postings than "Escape All" or "Strip disallowed tags" can provide individually.

Can you post the patch here so we can use it. That is exactly what I want to do.

Hi Leeland,

I'll try to post our patch, but we have a few upcoming releases next week so I can't promise a patch until after the releases.

In the meantime here's a quick rundown of what we did:
* Modified filter.module
* In filter_html_settings() function: added a new option to the list of filters called 'Escape Disallowed Tags'
* In filter_html() function: added new conditional (copy/pasted one of the others) that captures the new option created, except called a custom function escape_xss().
* Defined custom function escape_xss() that handles your escape/filter logic (customized by merging existing core "escape all" logic and filter_xss logic) : calls custom function escape_xss_split()
* Defined custom function escape_xss_split() based from filter_xss_split

In summary, like i mentioned in my earlier post, we just took the exisiting core logic for escaping and filtering (stripping disallowed tags), merged them into our custom functions, and created a new filter option that calls these custom functions.

Hope this helps, and if we have time we'll try to post a patch for you.

I added something like the attached to a 6.x site, but it doesn't appear to work as-is on 7.x+. Perhaps it's enough to get someone else started. Adding a parameter to filter_xss() and _filter_xss_split() feels a bit dirty.

Whoops, wrong version of my patch -- re-attaching. (Still doesn't work, though. ;)

Based on @Jeremy patch I've created patch for Drupal 7.x.

This is an exotic need. Let's not fill core with <1% needs.

This is a fairly reasonable change request, which would certainly help to make more sense of the combination of both filters.

I disagree, but okay.

My patch should be good but it has to be properly formatted, will do it in 1-2 weeks.

Here is the patch in proper format