SOLVED: Search Element Button/Icon: the span tag placed inside the text field is no longer interpreted

Bugs
1

Browser: Any
OS: Any

In the ‘Button/icon’ section, in version 2.3.11, the text could contain an element such as <span class"=myclass">my button text, which is permitted in a button from an HTML semantics perspective as span is not an interactive content.

text-field-button
text-field-button602×318 16.5 KB

button-icon-2.3.11
button-icon-2.3.111482×602 54.5 KB

Since version 2.3.12, the span tag is no longer interpreted as HTML but as plain text. Is there a reason for this change?

button-icon-2.3.12
button-icon-2.3.121796×760 76.5 KB

3

Hi,
Thanks for your report!

I can see the behavior change you are referring to, but I cannot confirm from the current context whether this was an intentional sanitization change or an unintended regression.

We will need to confirm this internally.

4

Seems to be the same root cause as this one: WIP: <a> tag not working anymore in form after update.

6

Yes, I saw it. I think it can be related to the same behaviour

8

We’ve addressed this in Bricks 2.3.13, now available as a one-click update in your WordPress Dashboard.

Allowed inline HTML in the Search element’s button text now renders correctly again.

Please read the changelog entry before updating, and let us know if you experience any issues.