Follow-up to #2501441: Document SafeMarkup::set in AllowedTagsXssTrait::fieldFilterXss

Problem/Motivation

AllowedTagsXssTrait::fieldFilterXss() can add a lot of long strings into memory in the SafeMarkup list.

Proposed resolution

Free the memory, based on one of these:

Remaining tasks

User interface changes

API changes

Comments

xjm’s picture

Issue tags: +SafeMarkup
xjm’s picture

cilefen’s picture

Title: Free strings added to the SafeMarkup list AllowedTagsXssTrait::fieldFilterXss() when they are no longer needed » Free strings added to the SafeMarkup list in AllowedTagsXssTrait::fieldFilterXss() when they are no longer needed
star-szr’s picture

What's the status here now that #2506195: Remove SafeMarkup::set() from Xss::filter() is in?

cilefen’s picture

The Xss::filter() call in AllowedTagsXssTrait::fieldFilterXss() no longer adds strings to memory.

mgifford’s picture

Status: Postponed » Active

There doesn't seem to be anything to postpone this on anymore.

cilefen’s picture

I followed the call chain and it looks to be the case that we get something implementing SafeStringInterface but these calls do not bloat the safe strings list. Can someone else verify that?

Berdir’s picture

Status: Active » Closed (won't fix)

Yes, it's safe to say that this doesn't happen anymore I think.