[BUG] Header inline style no longer works (possible regression)

[RRRRela]

Please confirm the following

• I have read and agree to AGPL-3.0 Section 15 .
  The program is provided "as is" without any warranties; you bear all risks of using it.

• I have read and agree to AGPL-3.0 Section 16 .
  The copyright holders and distributors are not liable for any damages resulting from the use or inability to use the program.

• I confirm my description is clear, polite, helps developers quickly locate the issue, and complies with community rules.

• I have read the OpenList documentation.

• I confirm there are no duplicate issues or discussions.

• I confirm this is an OpenList issue, not caused by other reasons (such as network, dependencies, or operation).

• I believe this issue must be handled by OpenList and not by a third party.

• I confirm this issue is not fixed in the latest version.

• I have not read these checkboxes and therefore I just ticked them all, Please close this issue.

OpenList Version (required)

v4.2.1

Storage Driver Used (required)

Local

Bug Description (required)

Hi,

I noticed a change in behavior regarding HTML rendering in the header.

In previous versions, inline styles worked as expected. For example:

Test

would render as red text.

However, in the current version, the style attribute appears to be stripped or ignored, and the text is rendered without styling.

Steps to reproduce:

1. Set header content to:

   Test

2. Open the page

Expected behavior:
Inline styles (e.g., color) should be applied.

Actual behavior:
The style attribute is removed or not applied.

Additional context:
I saw recent changes related to filtering content (e.g., "Move FilterReadMeScripts to frontend"), so I’m not sure whether this is intentional or a regression.

Is this behavior expected?

Thanks.

Logs (required)

No relevant logs.

Configuration File Content (required)

No relevant configuration.

Reproduction Link (optional)

Not publicly accessible.

[xrgzs]

Is this behavior expected?

Yes.

Move FilterReadMeScripts to frontend

You can try the beta version, as it hasn’t been officially released yet.

If you trust the content, you can disable the filter.