HTML Block elements & Textareas

[davidthor]

Just tried creating a new HTML Block element using a textarea instead of an input and got quite a few bugs in the process:

Screenshot: http://i.imgur.com/VyyILhy.png?1

Console also produces the following line on keypress after the iframe has attempted to load the change:

30 sec timeout not done: 65027 seconds left       page-tracking.js?ver=3.8.1:402

[atwellpub]

Confirmed the issue. Going to let David take a look at this one.

[DavidWells]

What HTML was being used in the input?

On Feb 27, 2014, at 12:12 PM, David Thor notifications@github.com wrote:

Just tried creating a new HTML Block element using a textarea instead of an input and got quite a few bugs in the process:

Screenshot: http://i.imgur.com/VyyILhy.png?1

Console also produces the following line on keypress after the iframe has attempted to load the change:

30 sec timeout not done: 65027 seconds left page-tracking.js?ver=3.8.1:402 — Reply to this email directly or view it on GitHub.

[davidthor]

<div class='form-group'>
<textarea class='form-control' placeholder='Message'></textarea>
</div>

[DavidWells]

You can't use other form inputs in the custom HTML box. You would need to make text areas out of the text area field input in the dropdown.

But try double quotes instead of single ones it might work. It might break the preview screen but render correctly when shortcode is used on a page

On Feb 27, 2014, at 1:04 PM, David Thor notifications@github.com wrote:

— Reply to this email directly or view it on GitHub.

[davidthor]

Whenever trying to use double quotes in the HTML input box it gets automatically changed to a single quote.

Is there any chance of support of other field inputs in the future? Textarea in particular would be crucial for me.

[DavidWells]

There is a textarea option built in. You would need to use that. You can apply any custom CSS you want to the forms after the fact

[davidthor]

I've seen the feature, but I prefer to use my own html where possible so as to avoid making changes CSS changes on a per-plugin basis. It seems odd to keep adding to my CSS file only to have the CSS applied to one or two elements.

On Thursday, February 27, 2014, David Wells notifications@github.com wrote:

[image: textarea option]https://f.cloud.github.com/assets/532272/2288241/939a486c-9ff7-11e3-82d1-bc15fed63512.jpg

There is a textarea option built in. You would need to use that. You can apply any custom CSS you want to the forms after the fact

Reply to this email directly or view it on GitHubhttps://github.com/inboundnow/leads/issues/32#issuecomment-36294765 .

[DavidWells]

The tool is meant to be super simple for non technical people to use. Adding in custom ids and class names etc would add a ton of confusion to the creation process. We are trying to avoid form option overload wherever possible.

I'd recommend gravity forms if you want to do a ton of custom stuff. Or wait for future release with CF7 updates

You can add the inbound form classes to your css like

.existing-form-class, .inbound-form-class {
//stuff
}