# Escape input - block level content attribute\[input, textarea, auto controlls\]

**URL:** <https://forum.pinegrow.com/t/escape-input-block-level-content-attribute-input-textarea-auto-controlls/8696>\
**Category:** Bug Reports\
**Tags:** wordpress, gutenberg\
**Created:** [February 5, 2024, 9:24am UTC](https://forum.pinegrow.com/t/escape-input-block-level-content-attribute-input-textarea-auto-controlls/8696 "2024-02-05T09:24:12Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Bear](https://avatars.discourse-cdn.com/v4/letter/b/ac8455/32.png) [@Bear](https://forum.pinegrow.com/u/Bear)\
**Post date:** [February 5, 2024, 9:24am UTC](https://forum.pinegrow.com/t/escape-input-block-level-content-attribute-input-textarea-auto-controlls/8696/1 "2024-02-05T09:24:12Z")

</div>

Hi there!

Correct me if I am wrong!

I’ve just stumbled upon “bug” where using Block level content attribute with control such as input, or textarea and perhaps auto - does not escape \<\> - which can lead to unexpected behaviour. So for example if someone has custom block with such attribute - from panel controls person can input the \<\> tags, script and etc. Perhaps someone needs this kind of behaviour.

Although to be on a safe side - if someone requires such a behaviour perhaps checkbox could appear in Pinegrow “escape input”? I understand that additional logic is required in the output of code generation.

On the other hand - when using rich text - it does behave as intended(this statement has not been tested extensively).