For your content pages you can run the following to disable the email cloaking: {emailcloak=off}

Hello @Bloggerschmidt,

Thank you for your contribution.

The last comment here was on 20 July 2015. So the question is, Is this issue/pull request still valid?
If no reply is received within 4 weeks we will close this issue.

In case the issue still exists, can you please provide clearer step-by-step instructions.

Thanks for understanding!

The issue is still valid. I am not a regular expression person to solve this. It needs to check to see if the email is within a input field as a value.

It needs to check to see if the email is within a input field as a value.

@spignataro this doesn’t sound quite correct, cloaking is supposed to check in the content area.
Input fields are not quite used there and should be part of a form. Also input fields use the javascript validation and the server side validation for an email input. I would say that this is a very odd use case.

I would have to disagree. I have many clients whom put in forms on their content pages. I have stopped putting in anything in the value field because of this bug. It just needs to check to see if the value has a email address and if it does just skip over the cloaking.

@spignataro As this isssue has no code attached, can you provide a way to reproduce this issue, we can then look at adding the needed code.

Put in code into the input area:

<input value="mail@example.com" size="20" name="form[EMail]" id="EMail" class="rsform-input-box" type="text">

with the plugin turned on take a look at the marketup.

here is a PR for that issue: #8039